Systems and methods to utilize smart components

ABSTRACT

Systems, methods, and machine-readable hardware to facilitate a diagnosis of a failure of a first part in a vehicle. The system receives a maintenance message, over a network at a network-based marketplace. The maintenance message includes characterization information received from a component in the vehicle. The component includes a sensor that senses the first part to generate the characterization information. The system identifies sub-system processing rules based on the maintenance message and executes the sub-system processing rules. The sub-system processing rules cause a smart component engine to perform operations comprising identifying a sub-system and scanning the sub-system responsive to identifying an increase in a likelihood of failure of the first part based on the characterization information. The first sub-system includes a plurality of parts and the scanning includes scanning the plurality of parts to retrieve characterization information from the plurality of parts to identify original equipment authentication information.

CLAIM OF PRIORITY

This application is a continuation of and claims the benefit of priorityof U.S. application Ser. No. 14/588,272, filed Dec. 31, 2014, which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates to computing and data processing systems. Moreparticularly, systems and methods to utilize smart components aredescribed.

RELATED

Vehicle repair involves identifying parts that have failed, utilizingprocedures or employing services to make a repair and economizing thecosts that are often incurred to implement these activities. Today, mostvehicle owners wait for a part to fail before considering the abovedescribed activities.

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in the drawings that form a part of thisdocument: Copyright eBay, Inc. 2014, All Rights Reserved.

BRIEF DESCRIPTION OF DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 illustrates a system to utilize smart components, according to anembodiment;

FIG. 2 illustrates a mobile device, according to an embodiment;

FIG. 3A illustrates monitor information, according to an embodiment;

FIG. 3B illustrates vehicle information, according to an embodiment;

FIG. 3C illustrates part description information, according to anembodiment;

FIG. 4A illustrates a maintenance message, according to an embodiment;

FIG. 4B illustrates a synchronization message, according to anembodiment;

FIG. 5 illustrates a network-based marketplace, according to anembodiment;

FIG. 6A illustrates an items table, according to an embodiment;

FIG. 6B illustrates a listing, according to an embodiment;

FIG. 7A illustrates a user table, according to an embodiment;

FIG. 7B illustrates user profile information, according to anembodiment;

FIG. 7C illustrates user information, according to an embodiment;

FIG. 7D illustrates maintenance information, according to an embodiment;

FIG. 7E illustrates part maintenance information, according to anembodiment;

FIG. 7F illustrates smart component processing information, according toan embodiment;

FIG. 7G illustrates a method to utilize a smart component, according toan embodiment;

FIG. 7H illustrates a method to utilize a smart component, according toan embodiment;

FIG. 7I illustrates a user interface, according to an embodiment;

FIG. 7J illustrates user interface, according to an embodiment;

FIG. 7K illustrates user interface, according to an embodiment;

FIG. 8A illustrates a system to utilize an electronic garage shelf,according to an embodiment;

FIG. 8B illustrates a network-based marketplace, according to anembodiment;

FIG. 8C illustrates a user table, according to an embodiment;

FIG. 8D illustrates garage shelf commands, according to an embodiment;

FIG. 8E illustrates virtual part information, according to anembodiment;

FIG. 8F illustrates a virtual part, according to an embodiment;

FIG. 8G illustrates token part information, according to an embodiment;

FIG. 8H illustrates a token part, according to an embodiment;

FIG. 8I illustrates a method to process commands, according to anembodiment;

FIG. 8J illustrates a method to alert a creation of a virtual part,according to an embodiment;

FIG. 8K illustrates a method to process virtual parts, according to anembodiment;

FIG. 8L illustrates a method to process token parts, according to anembodiment;

FIG. 8M illustrates a method to utilize an electronic garage shelf,according to an embodiment;

FIG. 8N illustrates a user interface, according to an embodiment;

FIG. 9A illustrates a system for multi-signal fault analysis, accordingto an embodiment;

FIG. 9B illustrates a test protocol, according to an embodiment;

FIG. 9C illustrates a network-based marketplace, according to anembodiment;

FIG. 9D illustrates user profile information, according to anembodiment;

FIG. 9E illustrates a fault analysis repository, according to anembodiment;

FIG. 9F illustrates user fault analysis information, according to anembodiment;

FIG. 9FF illustrates user test request information, according to anembodiment;

FIG. 9G illustrates system fault analysis information, according to anembodiment;

FIG. 9GG illustrates system test request information, according to anembodiment;

FIG. 9H illustrates test design information, according to an embodiment;

FIG. 9I illustrates multi-signal information, according to anembodiment;

FIG. 9J illustrates correlation information, according to an embodiment;

FIG. 9K illustrates a signal message, according to an embodiment;

FIG. 9L illustrates a signal message, according to an embodiment;

FIG. 9M illustrates a method to process a test request, according to anembodiment;

FIG. 9N illustrates a method for multi-signal fault automated analysis,according to an embodiment;

FIG. 9O illustrates a method to identify test design information,according to an embodiment;

FIG. 9P illustrates a method to identify signal processing, according toan embodiment;

FIG. 9Q illustrates a method to analyze multi-signal information,according to an embodiment;

FIGS. 9R-9S illustrate user interfaces, according to an embodiment;

FIG. 10A illustrates a system for an e-commerce enabled digitalwhiteboard, according to an embodiment;

FIG. 10B illustrates a context panel, according to an embodiment;

FIG. 10C illustrates a shopping cart panel, according to an embodiment;

FIG. 10D illustrates a metadata panel, according to an embodiment;

FIG. 10E illustrates a search panel, according to an embodiment;

FIG. 10F illustrates a tool panel, according to an embodiment;

FIG. 10G illustrates a dialogue panel, according to an embodiment;

FIG. 10H illustrates a participant panel, according to an embodiment;

FIG. 10I illustrates a network-based marketplace, according to anembodiment;

FIG. 10J illustrates user profile information, according to anembodiment;

FIG. 10K illustrates context directory information, according to anembodiment;

FIG. 10L illustrates a context, according to an embodiment;

FIG. 10M illustrates request information, according to an embodiment;

FIG. 10N illustrates a session, according to an embodiment;

FIG. 10O illustrates a request, according to an embodiment;

FIG. 10P illustrates response information, according to an embodiment;

FIG. 10Q illustrates feature element information, according to anembodiment.

FIG. 10R illustrates a method, according to an embodiment, to add acontext;

FIG. 10S illustrates a method, according to an embodiment, to attach acontext;

FIG. 10T illustrates a method, according to an embodiment, to receiveand process a request;

FIG. 10U illustrates a method, according to an embodiment, to process arequest based on a context;

FIG. 11 is a block diagram illustrating an example embodiment of ahigh-level client-server-based network architecture;

FIG. 12 is a block diagram illustrating an example embodiment of apublication system;

FIG. 13 is a block diagram illustrating tables that are utilized by thepublication system, according to an embodiment; and

FIG. 14 is a block diagram of a machine in an example form of acomputing system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the present invention. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide an understanding of anembodiment of the inventive subject matter. It will be evident, however,to those skilled in the art that embodiments of the inventive subjectmatter may be practiced without these specific details. In general,well-known instruction instances, protocols, structures, and techniqueshave not been shown in detail.

Systems and Methods to Utilize Smart Components

FIG. 1 illustrates a system 100, according to an embodiment, utilizingsmart components 102. The system 100 may include a vehicle 104 thatincludes smart components 102 that are grouped into sub-systems 103(e.g., chassis, engine, suspension, etc.). While the vehicle 104 isillustrated as an automobile, it will be appreciated that trucks,all-terrain vehicles, jeeps, aircraft, water-born vessels, spacevessels, and the like may embody the illustrated vehicle 104. Each smartcomponent 102 may include a part 106 and a sensor 108. Broadly, thesmart component 102 may utilize the sensor 108 to sense the part 106 toreceive information (e.g., a sense of the part) that is utilized by thesmart component 102 to generate characterization information andcommunicate the characterization information (e.g., percentage wear)over a network 110 (e.g., nearfield communication (NFC)) to a mobiledevice 112 (e.g., smart phone, Apple iPhone, etc.) that, in turn,communicates a maintenance message that includes the characterizationinformation over a network 116 (e.g., cellular, WiFi, Internet,telephone, etc., combinations thereof) to a network-based marketplace118 that, in turn, stores the characterization information and otherinformation and processes the characterization information to initiateelectronic commerce activity. Merely for example, a smart component 102in a Ford Mustang may include a sensor 108 for a brake pad that senseswear (e.g., ninety percent) for the brake-pad, the smart component 102to generate the characterization information based on the sensing of thesensor and to communicate the characterization information over thenetwork 110 (e.g., NFC) to an iPhone that, in turn, communicates themaintenance message over a network 116 (e.g., cellular and Internet) toa network-based marketplace 118 that, in turn, stores thecharacterization information in an electronic garage for the FordMustang in the user profile associated with the iPhone, identifies aservice level for the brake-pad, and generates a triggering event thatis processed to initiate electronic commerce activity. For example, thenetwork-based marketplace 118 may identify one or more sets ofprocessing rules based on the triggering event, and execute the one ormore sets of processing rules to initiate electronic commerce and otherrelated activities. In one embodiment, one set of processing rules mayidentify the location of the iPhone that originated the maintenancemessage to initiate electronic commerce activity. For example, if thelocation of the iPhone is identified to be in the vicinity of a brakeshop, the network-based marketplace 118 may respond to the maintenancemessage by generating and sending a user interface to the iPhone thatprovides an estimated time for the brake shop to install the brake pad.

The smart components 102, network 110, mobile device 112, network 116,and network-based marketplace 118 are further described. Each smartcomponent 102 may include a sensor 108 that senses an associated part106. The smart component 102 may generate characterization informationbased on the sensing of the part 106 and communicate thecharacterization information that characterizes the current state of thepart 106. For example, the characterization information may includeperformance information, percentage wear information, state informationor the like. In accordance with one embodiment, the smart component 102illustrated on the lower left of FIG. 1 is illustrated as including apart 106 that is adapted to receive a sensor 108 and the smart component102 to its immediate right is manufactured to include the sensor 108.For example, the smart component 102 on the left includes a sensor 108that is affixed to the part 106 as a subsequent assembly rather thanbeing designed and manufactured as such (e.g., factory embedded). Smartcomponents 102 may be manufactured and adapted for brake systems,filters, suspension systems, belts, bulbs sparks, batteries, tire walls,etc. Merely for example, smart components 102 for the brake system maysense and communicate characterization information for pads and rotors.Smart components 102 for filters may sense and communicatecharacterization information for oil filters, fuel filters and airfilters. Smart components 102 for a suspension system may sense andcommunicate characterization information for springs, leafs and shocks.Sensors 108 may sense and report information that characterizesdifferent aspects of the part 106. For example, a sensor 108 maycharacterize acceleration, separation, deformation, impact/shock,water/moisture, temperature, pressure, fluid flow, fluid levels or anyother quantifiable natural phenomena. In the case of separation, a gapmay be sensed between paired sensors 108 and characterized by one orboth of the sensors 108. In the case of deformation, damage may besensed on a part 106 in a package before the package is opened. Furtherin the case of deformation, one or more sensors 108 may sense andcharacterize vibration, bend, flex, strain, and weight.

The network 110 may be embodied as a wireless network, near frequencynetwork (NFC), radio frequency network (e.g., RFID)) or some other typeof network capable of supporting communication between a smart component102 and the mobile device 112. The mobile device 112 may include a smartphone such as an iPhone, Nokia, or BlackBerry. Further, the mobiledevice 112 may utilize the Android mobile operating system to provideservices described in this document. It will be appreciated by onehaving ordinary skill in the art that the Android mobile operatingsystem is gaining public acceptance as an automotive operating system.The mobile device 112 may further include software in the form of anoperating system (e.g., open or proprietary) and one or moreapplications (e.g., apps) that may be uploaded to the mobile device 112to provide one or more functions that are described in this document.The network 116 may include a wireless network, near frequency network(NFC), radio frequency network (RFID), LAN, WAN, Internet, telephone, orany other type of network capable of supporting communication betweenthe mobile device 112 and the network-based marketplace 118. In anotherembodiment, the mobile device 112 may include any paired device, such asGoogle Glass, a smartwatch, etc.

The network-based marketplace 118 may be an electronic marketplace forpurchasing and selling items and services such as eBay of San Jose,Calif., “The Worlds Online Marketplace.” The items sold or purchased onthe network-based marketplace 118 may include the parts 106, the vehicle104, and other items and services related to the parts 106 and vehicle104. The network-based marketplace 118 supports electronic commerceservices (e.g., search, browse, merchandise, expert services, etc.) tofacilitate the replacement and repair of the parts 106 for the vehicle104, as is described in this document. The client machine 120 mayinclude a mobile device 112, desktop computer, laptop computer or anyother device from which a user (e.g., buyer, seller, etc.) may accessand utilize the services of the network-based marketplace 118.

FIG. 2 illustrates a mobile device 112, according to an embodiment. Themobile device 112 may include a maintenance application 200, applicationresources 202, database 204 and a wireless reader 206. The maintenanceapplication 200 may include a communication module 208, a maintenancemodule 210, and other apps (not shown) that may be loaded onto themobile device 112. The communication module 208 may receive andcommunicate information. For example, the communication module 208 mayreceive commands from the operator of the mobile device 112 andinformation that originates from outside of the mobile device 112. Thecommands from the user may include a “system part scan” command to scanfor smart components 102 in a vehicle 104 in the immediate vicinity ofthe mobile device 112, a “sub-system part scan” command to scan forsmart components 102 in a sub-system (e.g., engine, chassis, brakes,etc.) of the vehicle 104, a “configure alerts” command to configure analert that notifies the user of mobile device 112 (e.g., responsive tothresholds being exceeded), and other commands. For example, the user ofthe mobile device 112 may configure an audible, haptic or visual alerton the mobile device 112 responsive to an identification of a thresholdbeing exceeded. In addition, mobile device 112 may be associated with auser profile on the network-based marketplace 118, and alerts may beconfigured to be communicated to any devices associated with the userprofile such as the client machine 120, as described in this document.In addition, the communication module 208 may receive characterizationinformation from smart components 102. For example, the characterizationinformation may include performance information, a percentage wear,state information or the like, as previously described. The maintenancemodule 210 may process the commands and the characterization informationreceived via the communication module 208. For example, the maintenancemodule 210 may update the database 204 with configuration information,cause the communication module 208 to send a command to thenetwork-based marketplace 118 (as shown in FIG. 1), or timestampcharacterization information that was reported by a smart component 102with the current time before storing the characterization information inthe database 204 and causing the communication module 208 to send amaintenance message to the network-based marketplace 118. Theapplication resources 202 may include static bulk data definitions andother static content (e.g., bitmaps, layout definitions, user interfacestrings, animation instructions, etc.) that may be utilized by themaintenance application 200.

The database 204 may include monitor information 212, forwardinginformation 214, and user information 216. The monitor information 212may store characterization information received from smart components102 and metadata related to the characterization information. Theforwarding information 214 may store information that describes othersystems or network-entities that are utilized for processing related tosmart components 102. For example, the forwarding information 214 mayinclude one or more entries that correspond to one or more entries ofuser profile information on the network-based marketplace 118. Forexample, the forwarding information 214 may be utilized to identifyother user profile information based on a vehicle 104 (e.g., via vehicleidentification number (VIN), possibly in combination with a shared‘family’ or ‘sharing’ code). The user information 216 may includeinformation related to the user associated with the mobile device 112including a user name, a user telephone number, and password forauthentication by the network-based marketplace 118. Further, the userinformation 216 may include a user identifier 218 that uniquelyidentifies the user on the network-based marketplace 118. The wirelessreader 206 may be attached to the mobile device 112 to receive thecharacterization information from the smart components 102.

FIG. 3A illustrates monitor information 212, according to an embodiment.The monitor information 212 may store information for vehicles 104. Forexample, a first entry of vehicle information 300 may store informationfor a Ford Mustang and a second entry of vehicle information 300 maystore information for a Chevrolet Camaro. In one embodiment, an entry ofvehicle information 300 may be automatically stored in the monitorinformation 212 responsive to receiving characterization informationfrom a particular vehicle 104 for the first time. According to oneembodiment, the vehicle information 300 may be stored in a provisionalstate until association with a particular vehicle 104 has beencorroborated through repeated recognition over time and location,possibly in conjunction with other already-associated orreliably-coincidental signals.

FIG. 3B illustrates vehicle information 300, according to an embodiment.The vehicle information 300 may store information for a vehicle 104. Thevehicle information 300 may include vehicle identification information302 that identifies a vehicle 104 and one or more entries of partdescription information 304 that describes part(s) 106 in the vehicle104. The vehicle identification information 302 may include a vehicleidentification number (VIN), make, model, and year for the vehicle 104.Each entry of part description information 304 corresponds to a part106. In one embodiment, an entry of part description information 304 maybe automatically stored in the vehicle information 300 responsive toreceiving characterization information for a part 106 for the first timefrom the vehicle 104.

FIG. 3C illustrates part description information 304, according to anembodiment. The part description information 304 may include a partidentifier 306, a part type identifier 308, part log information 310,maintenance history information 316, service level information 318, andoriginal equipment manufacturer (OEM) authentic information 320. Thepart identifier 306 may include an alphanumeric identifier or some otheridentifier that uniquely identifies the part 106. In accordance with oneembodiment, the part identifier 306 may include a range of partidentifiers 306. The part identifier 306 may be assigned by amanufacturer or the network-based marketplace 118. The part identifier306 may include a standard product identifier (e.g., Universal ProductCode (UPC), Electronic Product Code (EPC), etc.). The part typeidentifier 308 may identify a part type (e.g., hose, filter, bulb, belt,etc.). A particular part type identifier 308 may be associated with oneor more part identifiers 306. The part log information 310 may includeone or more entries of characterization information 312 for the part106. Each entry of characterization information 312 may be associatedwith a timestamp 314 that is generated by the mobile device 112 andstored with the corresponding characterization information 312 that isreceived from a smart component 102. In one embodiment, the part loginformation 310 may be embodied as a circular buffer with a size that isconfigurable. The characterization information 312 was previouslydescribed. The timestamp 314 may include the current time as identifiedby the mobile device 112 responsive to the mobile device 112 receivingthe characterization information 312. In one embodiment, the mobiledevice 112 may receive characterization information 312 for a part 106that signals a replacement of the part.

Responsive to receiving the characterization information 312, the mobiledevice 112 may purge an entry of part description information 304 forthe part 106 that is being replaced from the vehicle information 300 andcreate an entry of part description information 304 in the vehicleinformation 300 for the part 106 that is new. The maintenance historyinformation 316 may store a history for the part type identifier 308 andsurvive a replacement operation in conjunction with the part typeidentifier 308. The maintenance history information 316 may associateeach replacement of the part 106 with a timestamp 314 that includes adate and time of replacement, an odometer reading sampled at the time ofreplacement, a percentage wear of the part 106 replaced (e.g., 80%wear), the manufacturer of the part 106, the part identifier 306 andother information.

The service level information 318 may store the current service levelfor the part 106. In one embodiment, four service levels may be definedincluding “OK,” “SUGGEST,” “WARN”, and “REPLACE” in accordance withthresholds, as described later in this document. The first level, “OK,”may be utilized to indicate no thresholds have been exceeded. The secondlevel, “SUGGEST,” may be utilized to indicate at least one threshold wasexceeded causing the sending of an alert to the user that includes asuggestion. For example, the network-based marketplace 118 may send analert to the user including a suggestion to repair or purchase a part106. The third level, “WARN,” may be utilized to indicate at least onethreshold was exceeded causing the network-based marketplace 118 to sendan alert to the user including a suggestion to repair or purchase a part106 and a warning. For example, the alert may suggest to the user torepair or purchase a part 106 and warn the user that the current part106 is in need of repair. The fourth level, “REPLACE,” may be utilizedto indicate at least one threshold was exceeded causing the sending ofan alert to the user that includes a suggestion to repair or purchase apart 106 and an urgent warning. For example, the alert may suggest tothe user to repair or purchase a part 106 urgently warn the user thatthe part 106 may fail because a likelihood of failure has exceeded athreshold (e.g., fifty-percent).

The OEM authentic information 320 may include a flag that is asserted tosignify the part 106 is manufactured by an original equipmentmanufacturer (OEM) and not asserted to indicate otherwise (e.g.,knockoff-authentication failed). For example, the OEM authenticinformation 320 may be updated based on characterization information 312that is received from a smart component 102, the characterizationinformation 312 including results from a test that is performed on thepart 106 while it is in place in the vehicle 104. In one embodiment, thetest may generate characterization information 312 that includes a partidentifier 306 that, in turn, is compared with OEM tracking informationstored at the network-based marketplace 118 to identify whether the part106 in the smart component 102 was manufactured by any one of multiplemanufacturers. According to one embodiment, the mobile device 112 mayperform the comparison. According to one embodiment, the mobile device112 or the network-based marketplace 118 may identify (indirectly orotherwise) a certifiable cryptographic public key that is used todecrypt parts of the characterization information 312 (e.g., dynamic)where identification of characterization information 312 that is notencrypted or cannot be decrypted based on the public key causes themobile device 112 and/or network-based marketplace 118 to not assert theOEM authentic information 320 (e.g., the part 106 is fake because thefraudulent manufacturer does not possess the corresponding private keyto encrypt the part type identifier 308 in the characterizationinformation).

FIG. 4A illustrates a maintenance message 400, according to anembodiment. The maintenance message 400 may be communicated by themobile device 112 to the network-based marketplace 118. The maintenancemessage 400 may be sent by the mobile device 112 to the network-basedmarketplace 118 responsive to the mobile device 112 receivingcharacterization information 312 from a smart component 102. Themaintenance message 400 may include the user identifier 218, vehicleidentification information 302, part identifier 306, part typeidentifier 308, characterization information 312, and a timestamp 314,all as previously described. In other embodiments, the maintenancemessage 400 may include multiple entries of characterization information312 respectively paired with timestamps 314.

FIG. 4B illustrates a synchronization message 402, according to anembodiment. The synchronization message 402 may be utilized by themobile device 112 to synchronize the network-based marketplace 118 withthe mobile device 112 in accordance with the information included in thesynchronization message 402. The synchronization message 402 may includethe user identifier 218, the vehicle identification information 302, andpart description information 304, all as previously described. Thesynchronization message 402 may be utilized to synchronize thenetwork-based marketplace 118 with the mobile device 112 with regard toa part 106. In other embodiments, the synchronization message 402 mayinclude multiple entries of part description information 304 tosynchronize the network-based marketplace 118 with the mobile device 112with regard to a vehicle 104.

FIG. 5 illustrates the network-based marketplace 118, according to anembodiment. The network-based marketplace 118 may include smartcomponent modules 500 and a database 204. The smart component modules500 may receive and process communications from the mobile device 112and the network-based marketplace 118. The communications from themobile device 112 may include the previously described maintenancemessage 400 and synchronization message 402. The communications from thenetwork-based marketplace 118 may include triggering events that aregenerated by the network-based marketplace 118. The smart componentmodules 500 may include a receiving module 502, a processing module 504,and a smart component engine 505. The receiving module 502 may receivethe communications and the processing module 504 may process thecommunications. In some instances, the processing module 504 may furthergenerate a triggering event based on the communication and communicatethe triggering event to the smart component engine 505 for furtherprocessing although other processes may generate and communicate atriggering event to the smart component engine 505. The database 204 mayinclude an items table 506, a user table 508, original equipmentmanufacturing (OEM) tracking information 510, maintenance information512, and smart component processing information 514. The items table 506may include multiple entries of listings with each listing describing anitem (e.g., part 106 or service) that is being offered for sale and/orfor auction on the network-based marketplace 118. The user table 508 mayinclude multiple entries of user profile information where each entry ofuser profile information may be utilized to describe a user (e.g.,buyer, seller, both) on the network-based marketplace 118. The OEMtracking information 510 may be utilized by the network-basedmarketplace 118 to perform a validation on a part 106 to identifywhether it is authentically supplied by a manufacturer. For example, themobile device 112 may be used to scan a part identifier 306 and/or parttype identifier 308 for a part 106 prior to installation in the vehicle104 to authenticate whether the part 106 is supplied by a particularmanufacturer. The maintenance information 512 may be utilized toidentify and execute a maintenance policy responsive to identifyingcharacterization information 312 or a time derivative of one or moreentries of characterization information 312 as exceeding or droppingbelow a threshold. For example, traversing a threshold may cause animplementation of a maintenance policy by communicating one or moretriggering events to the smart component engine 505. The smart componentprocessing information 514 may be utilized to define triggering eventsthat are received by the smart component engine 505, define processingrules that are executed by the smart component engine 505 responsive toreceiving a triggering event, and define associations between thetriggering events and the processing rules.

FIG. 6A illustrates the items table 506, according to an embodiment. Theitems table 506 may include entries of listings 600 that are publishedby sellers on the network-based marketplace 118.

FIG. 6B illustrates the listing 600, according to an embodiment. Thelisting 600 may describe an item that is offered for sale on thenetwork-based marketplace 118. The listing 600 may include a title 602,a part identifier 306 (optional), a part type identifier 308 (optional),a description 604, an image 606 of the item (e.g., part 106) that may beuploaded by the seller, a price 608 to purchase the item that may beconfigured by the seller, a bid 610 (e.g., the current highest bid forthe item), one or more categories 612 which may be navigated to locateand view the listing 600. The title 602 may briefly describe the itemand the description 604 may further describe the item. The title 602 andthe description 604 may be received from the seller. The part identifier306 may include a component/part identifier that identifies the part106. The part identifier 306 may be assigned by a manufacturer. The partidentifier 306 may include a global trade number (GTIN), a universalproduct code (UPC), a manufacture part number (MPN) or some otherstandard product identifier that identifies the item being described.

FIG. 7A illustrates a user table 700, according to an embodiment. Theuser table 700 may include multiple entries of user profile information702 that respectively correspond to a user who utilizes thenetwork-based marketplace 118 to buy and/or sell items (e.g., smartcomponents 102, parts 106, sensors 108, etc.).

FIG. 7B illustrates the user profile information 702, according to anembodiment. The user profile information 702 may include userinformation 216, user preference information 704, and garage information706. The user information 216 may store the name, address, telephonenumber, and other information, as described in FIG. 7C. The userpreference information 704 may store thresholds, values, and otherpreferences manually configured by the user or automatically configuredbased on behaviors or actions of the user. For example, the userpreference information 704 may store preferences for a particular brandof parts 106 that were identified based on user behavior includingpurchases, search queries, browsing values and the like that implicatedthe brand of a part 106. The garage information 706 may store vehicleinformation 300 for vehicles 104 that are associated with the user. Anentry of vehicle information 300 may be created or generated responsiveto a manual configuration by the user. In addition, an entry of vehicleinformation 300 may be automatically created or generated responsive toreceipt of a maintenance message 400 or synchronization message 402based on the content of the respective message.

FIG. 7C illustrates the user information 216, according to anembodiment. The user information 216 may include information thatdescribes the user, as mentioned above, such as a user identifier 218and expert information 220. The user identifier 218 may uniquelyidentify the user from other users on the network-based marketplace 118.The expert information 220 may include one or more part type identifiers308, one or more sub-system identifiers 708, and vehicle identificationinformation 302 that may identify one or more vehicles 104. For example,the expert information 220 may include an expertise level indicating theuser has an ability to provide “expert” or “qualified” advice for aparticular part 106, in a particular sub-system 103, in a particularvehicle 104, or some combination thereof. For example, the expertiselevel may indicate the user is a general expert who is qualified toprovide advice for Fords by including vehicle identification information302 that identifies Ford while specifying neither a part type identifier308 nor a sub-system identifier 708. Further for example, the expertiselevel may indicate the user is an expert for a specific type of hoses,in an engine sub-system for Fords.

FIG. 7D illustrates maintenance information 512, according to anembodiment. The maintenance information 512 may be used to facilitatethe maintenance of parts 106 on vehicles 104. The maintenanceinformation 512 may include one or more entries of part maintenanceinformation 710 that define thresholds and maintenance policies for aparticular part(s) 106.

FIG. 7E illustrates part maintenance information 710, according to anembodiment. The part maintenance information 710 may include vehicleidentification information 302 that identifies a vehicle 104, the parttype identifier 308 that identifies a type of a part 106 and part policyinformation 711. In some embodiments, the part maintenance information710 may further include a part identifier 306. The part policyinformation 711 may include threshold information 712 that includes athreshold in association with maintenance policy information 714 thatdefines maintenance for the associated threshold. For example, the partlog information 310 (FIG. 3C) for a smart component 102 may be processedto identify a computed value as exceeding threshold information 712 of75% (e.g., Level 1) to cause the associated maintenance policyinformation 714 to be implemented. In one embodiment, the maintenancepolicy information 714 may include a triggering event that iscommunicated to the smart component engine 505 for processing (e.g.,communicate alerts to mobile device 112). The part policy information711 may include multiple levels of threshold information 712 paired withmaintenance policy information 714 (e.g., “LEVEL 1,” “LEVEL 2,” “LEVEL3”). For example, the levels may be graduated based on the level of wear(e.g., 75%—“SUGGEST,” 85%—“WARN,” 95%—“REPLACE”).

FIG. 7F illustrates smart component processing information 720,according to an embodiment. The smart component processing information720 may include triggering event information 722 that defines triggeringevents, processing rules information 724 that includes sets ofprocessing rules, and association information 726 to associate eachtriggering event to one or more sets of processing rules. The smartcomponent processing information 720 may be utilized by the smartcomponent engine 505 to associate a triggering event with one or moresets of processing rules based on the association information 726, loadthe one or more sets of processing rules into the smart component engine505 and execute the one or more sets of processing rules.

Maintenance Message Triggering Event

The triggering event information 722 may include a maintenance messagetriggering event. The maintenance message triggering event may becommunicated by the processing module 504 to the smart component engine505 responsive to receipt of the maintenance message 400 at thenetwork-based marketplace 118. Recall that the mobile device 112 mayreceive characterization information 312 from a smart component 102(e.g., part 106 and sensor 108), the mobile device 112, in turn,communicating a maintenance message 400, including the characterizationinformation 312, to the network-based marketplace 118 including theprocessing module 504 that, in turn, processes the maintenance message400 to communicate the maintenance message triggering event to the smartcomponent engine 505. For example, the processing module 504 may processthe maintenance message 400 for the part 106 (e.g., engine hose) toidentify a new service level (e.g., “REPLACE,” “WARN,” “SUGGEST”) in theservice level information 318 for the part 106. Further, the associationinformation 726 may be utilized by the smart component engine 505 toassociate the maintenance message triggering event with sub-system scanrules, and install time processing rules, according to one embodiment.According to another embodiment, additional or fewer sets of processingrules may be associated with the maintenance message triggering event.The sub-system processing rules may be executed by the smart componentengine 505 to identify a service level (e.g., “REPLACE,” “WARN,”“SUGGEST”) other than “OK” in the service level information 318 for thepart 106. If a service level other than “OK” is identified then thesub-system processing rules may further be executed to identify asub-system that includes the part 106, and communicate a message to themobile device 112 that causes the mobile device 112 to scan all of thesmart components 102 in the identified sub-system. For example, anengine hose in an engine that is identified with a service level otherthan “OK” may be identified by the smart component engine 505 thatcauses a message to be communicated to the mobile device 112 that causesthe mobile device 112 to scan all the parts 106 in the identified enginesub-system. In one embodiment, related sub-systems may be scannedresponsive to identification of a service level other than “OK” for apart 106. In one embodiment, the scan of the sub-system is not performedif the engine-sub system or the entire vehicle 104 was scanned in apredetermined period of time (e.g., five minutes) prior to receipt ofthe maintenance message 400 by the network-based marketplace 118. In oneembodiment the period of time may be configured. In another embodiment,a part scan, sub-system part scan, or vehicle part scan may optionallyor automatically be delayed to enable the car to warm up, or otherwisereach a stable operating condition.

The install time processing rules may be utilized by the smart componentengine 505 to identify a service level (e.g., “REPLACE,” “WARN,”“SUGGEST”) other than “OK” in the service level information 318 for thepart 106. If a service level other than “OK” is identified thesub-system processing rules may further be executed to generate anestimated replacement time for the part 106, and communicate an alert tothe mobile device 112 that includes the replacement time. In oneembodiment, the replacement time may be computed based on the locationof the mobile device 112. For example, responsive to the smart componentengine 505 identifying the mobile device 112 as being located in ageographic circle that includes the garage of the user, the smartcomponent engine 505 may compute the replacement time for the part 106based on the assumption that the user is performing the replacement andthe competence level of the user. Further, for example, responsive tothe smart component engine 505 identifying the mobile device 112 asbeing located within a geographic circle that includes a vehicle repairshop, the smart component engine 505 may compute the replacement timebased on the competence level of the repair shop. In one embodiment, thecenter of the circle is the location of the mobile device 112 and theradius of the circle is a predetermined length. In one embodiment thelength of the radius may be configured. In another embodiment, ageographic area may further include an irregular region or set ofregions that are determined from navigation route information,calculated travel paths between common destinations (e.g.,home-to-work), or historical location information (with or withoutrespect to any specific travel path).

Alert Configuration Triggering Event

The triggering event information 722 may include an alert configurationtriggering event. The alert configuration triggering event may becommunicated by the mobile device 112 or client machine 120 to the smartcomponent engine 505, via the network-based marketplace 118, responsiveto receipt of one or more selections at the respective mobile device 112or client machine 120. The alert configuration triggering event mayinclude configuration information that is used to configure thresholdinformation 712 and maintenance policy information 714 for a particularpart 106. The association information 726 may be utilized by the smartcomponent engine 505 to associate the alert configuration triggeringevent with the alert configuration processing rules that, in turn, areexecuted by the smart component engine 505 to receive the configurationinformation, process the configuration information to generate thethreshold information 712 and maintenance policy information 714, storethe threshold information 712 in the part policy information 711 that isidentified for the part 106, and store the maintenance policyinformation 714 in the part policy information 711 that is identifiedfor the part 106.

Expert Request Triggering Event

The triggering event information 722 may include an expert requesttriggering event. The expert request triggering event may be sent by themobile device 112 or client machine 120 to the smart component engine505, via the network-based marketplace 118, responsive to receipt of aselection at the respective mobile device 112 or client machine 120. Theexpert request triggering event may include a part type identifier 308and/or sub-system identifier 708 and/or vehicle identificationinformation 302. The association information 726 may be utilized by thesmart component engine 505 to associate the expert request triggeringevent with the alert expert processing rules that, in turn, are executedby the smart component engine 505 to identify experts in the userinformation 216 based on the expert information 220. For example, thesmart component engine 505 may execute the alert expert processing rulesto identify experts in the user information 216 by matching the parttype identifier 308 and/or sub-system identifier 708 and/or vehicleidentification information 302 in the expert request triggering eventwith the expert information 220 in the user information 216 andcommunicating the results back to the respective mobile device 112 orclient machine 120 that initiated the request.

Manual Request Triggering Event

The triggering event information 722 may include a manual requesttriggering event. The manual request triggering event may be sent by themobile device 112 or client machine 120 via the network-basedmarketplace 118, in response to receipt of a selection at the respectivemobile device 112 or client machine 120. For example, a user who isoperating his mobile device 112 may be attempting to replace a part 106in his vehicle 104 in his garage at home and make a selection on hismobile device 112 to request a manual to repair a particular part 106.The manual request triggering event may include a part identifier 306and/or, a part type identifier 308 and/or sub-system identifier 708and/or vehicle identification information 302. The associationinformation 726 may be utilized by the smart component engine 505 toassociate the manual request triggering event with the manual processingrules which are executed by the smart component engine 505 to identifyand communicate the appropriate manual(s) to the mobile device 112 orclient machine 120.

Maintenance History Triggering Event

The triggering event information 722 may include a maintenance historytriggering event. The maintenance history triggering event may be sentby the mobile device 112 or client machine 120 to the smart componentengine 505, at the network-based marketplace 118, responsive to receiptof a selection at the mobile device 112 of the client machine 120. Forexample, a user who is operating his mobile device 112 may want to knowthe maintenance history of one or more parts 106 in his vehicle 104 andmake one or more selections on his mobile device 112 which causes themobile device 112 to communicate the maintenance history triggeringevent to the network-based marketplace 118. The maintenance historytriggering event may include a part identifier 306 and/or, a part typeidentifier 308 and/or sub-system identifier 708 and/or vehicleidentification information 302. The association information 726 may beused by the smart component engine 505 to associate the maintenancehistory triggering event with the maintenance history processing ruleswhich, in turn, are executed by the smart component engine 505 toretrieve one or more entries of maintenance history information 316 fromthe corresponding entries part description information 304 for one ormore parts 106, parts 106 included in one or more sub-systems and parts106 included in one or more vehicles 104 and to communicate themaintenance history information 316 that was retrieved to the mobiledevice 112 or client machine 120.

Merchandise Request Triggering Event

The triggering event information 722 may include an entry for amerchandise request triggering event. The merchandise request triggeringevent may be sent by a process in the network-based marketplace 118 tothe smart component engine 505 responsive to an identification of apresentation of merchandising information. For example, a user who isoperating his mobile device 112 or the client machine 120 may betargeted for a presentation of merchandising information (e.g.,presentation of purchase opportunities) that is updated or modified bythe smart component engine 505 to include purchase opportunities forparts 106 that are identified by the smart component engine 505.Responsive to receipt of the merchandise request triggering event, thesmart component engine 505 may utilize the association information 726to associate the merchandise request triggering event with themerchandise suggestion processing rules which, in turn, are executed bythe smart component engine 505 to identify service level information 318in the vehicle information 300 of the garage information 706 that isassociated with the user of the mobile device 112 or client machine 120.Responsive to identifying service level information 318 that is not “OK”(e.g., “SUGGEST,” “WARN,” “REPLACE”) for parts 106 of vehicles 104 inthe garage information 706 at the network-based marketplace 118, thesmart component engine 505 may utilize the associated maintenancehistory information 316 to modify the merchandising information. Forexample, the smart component engine 505 may identify parts 106 withservice level information 318 that are not “OK” and modify themerchandising information to include merchandising content for one ormore of the identified parts 106 where the merchandising content ismodified to include buying opportunities for the identified parts 106that are filtered according to the brands that are preferred by the useras determined by the corresponding maintenance history information 316.For example, the smart component engine 505 may modify merchandisingcontent to push unsolicited content to a user, realize an intra-purchaseopportunity with a suggestion (e.g., “Do you also need X” or “Otherusers often purchase Y” or “Purchase Z at the same time and save XX %”),realize a post-purchase opportunity with a suggestion (e.g., “You mightalso like”). For example, the smart component engine 505 may modifymerchandising content to present a wish list of parts 106 and sendalerts to any device associated with the current user (e.g., anotherdevice on which the user is running and signed-into amarketplace-connected app) (e.g., any device that has been indirectlyassociated with the user's profile—for example, given an operatingsystem or environment in which the user profile information 702 isassociated with a cloud account).

Purchase Request Triggering Event

The triggering event information 722 may include an entry for a purchaserequest triggering event. The purchase request triggering event may besent by a process in the network-based marketplace 118 to the smartcomponent engine 505 responsive to an identification of a presentationof merchandising information at the time of purchase. The purchaserequest triggering event operates similar to the merchandise requesttriggering event.

Search Suggestion Triggering Event

The triggering event information 722 may include an entry for a searchsuggestion triggering event. The search suggestion triggering event maybe sent by a process in the network-based marketplace 118 to the smartcomponent engine 505 responsive to an identification of a user enteringa query from a mobile device 112 or the client machine 120. In oneembodiment, an input box that receives a query from the user may includea drop-down box immediately below the input box. The drop-down box maycontain search suggestions that may be selected by the user to overwritethe current query. Responsive to receiving a search suggestiontriggering event, the smart component engine 505 may utilize theassociation information 726 to associate the search suggestiontriggering event to search suggestions processing rules that, whenexecuted by the smart component engine 505, identify parts 106 withservice level information 318 that is not “OK” (e.g., “SUGGEST,” “WARN,”“REPLACE”) for vehicles 104 in the garage information 706 or the user,and modify the search suggestions in the drop-down box to include searchsuggestions that target the identified parts 106. For example, the smartcomponent engine 505 may modify the search suggestions to includecategories, brands, performance characteristics, and compatibilityattributes based on the identified parts 106.

Location of Mobile Device Triggering Event

The triggering event information 722 may include an entry for a locationof mobile device triggering event. The location of mobile devicetriggering event may be sent by a scheduling process in thenetwork-based marketplace 118 to the smart component engine 505responsive to the expiration of a mobile device timer. The mobile devicetriggering event may be sent to identify the location of the mobiledevice 112 and initiate ecommerce activity. In one embodiment, themobile device timer may be reinitialized with a predetermined timeout offive minutes each time the triggering event is processed. In oneembodiment, the predetermined timeout may be configured by a user.Responsive to receiving a location of mobile device triggering event,the smart component engine 505 may utilize the association information726 to associate the mobile device triggering event with mobile devicelocation rules that, when executed by the smart component engine 505,identify the current location of the mobile device 112, identify parts106 with service level information 318 that is, respectively not “OK”(e.g., “SUGGEST,” “WARN.” “REPLACE”) for vehicles 104 in the garageinformation 706 of the user associated with a particular mobile device112, identify whether the current location of the mobile device 112 iswithin a geographic area (e.g., geographic circle) that includes afacility that may repair the identified part(s) 106, identify a waittime for the facility to perform the service, identify an estimatedrepair time to repair the part 106, communicate a message to the mobiledevice 112 that prompts the user of the opportunity to repair the part106 at the facility including an estimated wait time for the facility toperform the service and an estimated repair time for the facility torepair the part 106, and initialize the mobile device timer with thepredetermined timeout. In one embodiment, the center of the circle isthe location of the mobile device 112 and the radius of the circle is apredetermined length from the location of the mobile device 112. In oneembodiment the length of the radius may be configured.

Third Party Notification Triggering Event

The triggering event information 722 may include an entry for a thirdparty notification triggering event. Information may be communicated toa third party responsive to receiving this event. Responsive toreceiving a third party triggering event, the smart component engine 505may utilize the association information 726 to associate the third partynotification triggering event with third party triggering event rulesthat, when executed by the smart component engine 505, generate thirdparty information and communicate the third party information, over anetwork (e.g., network 116), to a third party (e.g., fleet management).For example, the third party information may include service levelinformation 318 for a part 106, maintenance history information 316 fora part 106, or any other information for a part 106, subsystem 103, orvehicle 104.

Recall/Bulletin Triggering Event

The triggering event information 722 may include an entry forrecall/bulletin triggering event. A recall/bulletin for one or moreparts 106 may be communicated to the mobile device 112 or client machine120 responsive to receiving a request from one of these devices for suchinformation. Responsive to receiving a recall/bulletin triggering event,the smart component engine 505 may utilize the association information726 to associate the recall/bulletin triggering event withrecall/bulletin rules that, when executed by the smart component engine505 cause the smart component engine 505 to identify garage information706 associated with a user associated with the client machine 120 ormobile device 112, identify one or more entries of vehicle information300 in the garage information 706 associated with the user, identifypart type identifiers 308 in the respective vehicle information 300 forwhich recall/bulletins have been published, and communicate therecall/bulletins to the mobile device 112 or client machine 120.

FIG. 7G illustrates a method 728 to utilize smart components, accordingto an embodiment. The method 728 may commence at operation 730, at thenetwork-based marketplace 118, with the receiving module 502 receiving amaintenance message 400 from a mobile device 112. For example, themobile device 112 may have received a selection to execute a part scan,sub-system scan part scan, or a vehicle scan for a vehicle 104.Responsive to execution of one of the aforementioned scans, the mobiledevice may receive characterization information 312 from a smartcomponent 102 on the vehicle 104 and communicate a maintenance message400 including the characterization information 312 and timestamp 314 tothe network-based marketplace 118.

At operation 732, the processing module 504 may identify the userprofile information 702 in the user table 700 based on the maintenancemessage 400.

At operation 734, the processing module 504 may store thecharacterization information 312 and the timestamp 314 as part loginformation 310 in the appropriate part description information 304(e.g., part 106). For example, the processing module 504 may identifythe vehicle information 300 in the garage information 706 in the userprofile information 702 based on the vehicle identification information302 in the maintenance message 400. In addition, the processing module504 may identify the appropriate part description information 304 in theidentified vehicle information 300 based on the part identifier 306 orpart type identifier 308 in the maintenance message 400. Finally, theprocessing module 504 may copy the characterization information 312 andthe timestamp 314 from the maintenance message 400 to next availablelocation in the part log information 310 in the identified partdescription information 304. In one embodiment, the processing module504 may create the vehicle information 300 in the garage information 706responsive to receipt of the maintenance message 400.

At decision operation 736, the processing module 504 may identifywhether a part 106 has not previously been registered in the garageinformation 706. For example, a part 106 that is not registered in thegarage information 706 may include replacing a part 106 that is old witha part 106 that is new for a particular part type identifier 308. If thepart identifier 306 in the maintenance message 400 is not found in thegarage information 706 then processing continues at operation 738.Otherwise, processing continues at operation 740.

At operation 738, the processing module performs multiple steps toregister the part 106. First, the processing module 504 may identify anexisting part 106 in the garage information 706 with a part typeidentifier 308 that matches the part type identifier 308 in themaintenance message 400. If found, the processing module 504 may utilizethe existing entry by overwriting the part identifier 306 that is oldwith the part identifier 306 that is new. Otherwise, the processingmodule 504 may create a new entry of part description information 304 inthe vehicle information 300. Second, the processing module 504 mayupdate the maintenance history information 316 for the part typeidentifier 308 by recording an entry chronicling the replacement of thepart 106 that is old with the part 106 that is new. For example, thebrand names of the two parts 106, the part identifiers 306, the parttype identifier 308, the current date, odometer reading, vehicleidentification information 302, and part log information 310 for thepart 106 that is old may be stored in the maintenance historyinformation 316. Third, the part identifier 306 for the part 106 that isbeing registered may be compared with the part identifiers 306 in theOEM tracking information. If a match is found, then the part 106 isvalidated as an authentic OEM part. Otherwise the part is not validatedas an authentic OEM part. In either instance, at operation 738, theprocessing module 504 may store the appropriate status in the OEMauthentic information 320 in the part description information 304 forthe part 106 and communicate the status to the associated client machine120 or mobile device 112. Fourth, the processing module 504 maycommunicate a recall/bulletin triggering event to the smart componentengine 505 to identify whether recall/bulletin notices are available forthe part 106 and, responsive to such an identification communicate analert to the mobile device 112 or client machine 120 that includes anotice of the recall/bulleting for the part 106.

At operation 740, the processing module 504 may compute a derivative ofpart log information 310 over time. The processing module 504 maycompute multiple derivatives of the part log information 310 including afirst-derivative to generate first-derivative information (e.g., asimple change over time (e.g., the average wear rate)), a secondderivative to generate second derivative information (e.g., anacceleration over time (e.g., the rate at which the rate ischanging—acceleration may indicate partial failure, failure in relatedparts, conditions exceeding some ‘elastic’ threshold, etc.)), and/or athird derivative to generate third derivative information (e.g., a‘jerk’—the rate at which the acceleration is changing—a sudden ‘jerk’possibly indicating a catastrophic failure or other transient butsignificant change not following the ‘usual’ degradation). For example,processing module 504 may generate first-derivative information for anaggregate often entries of characterization information 312. Thequantity of time may be computed by subtracting a timestamp 314associated with the first entry (e.g., earliest) in the aggregate fromthe timestamp 314 associated with the last entry (e.g., latest) in theaggregate. Further, the quantity of wear may be computed by subtractingthe characterization information 312 associated with the first entry(e.g., earliest) in the aggregate from the characterization information312 associated with the last entry in the aggregate. Further, where thefirst-derivative is computed by dividing the quantity of wear by thequantity of time and, optionally, by smoothing the resulting derivative.

At decision operation 742, the processing module 504 may compare thefirst derivative information and/or the second derivative informationand/or the third derivative information with respective thresholdinformation 712 in the part maintenance information 710 associated withthe part type identifier 308 to identify whether a threshold has beenexceeded. If a threshold is exceeded then processing continues atoperation 744. Otherwise, processing continues at operation 746. In oneembodiment, the threshold may be calculated dynamically at the timeoperation 742 is executed by the processing module 504. At operation744, the processing module 504, may register the one or more thresholdsthat have been exceeded.

At operation 746, the processing module 504 may interrogate the part loginformation 310 to identify anomalous part log information 310. Theprocessing module 504 may identify anomalous part log information 310 inmany different ways. For some part types (e.g., part type identifier(s)308), the processing module 504 may expect the part log information 310to represent a discrete approximation or sampling of a continuous setwhose ideal trend is expected to progress in one direction, afteraccounting for measurement noise due to sensor 108 and extremeenvironmental conditions. For example, brake wear is ideally expected totrend smoothly from 0% to 100% wear. In this instance it is reasonableto apply averaging or outlier elimination to obtain a more accurateapproximation of actual wear level. Consequently, a single anomalousreading may not be considered actionable. In contrast, other parts 106may supply measurements that result in part log information 310 that islargely uncorrelated to other measurements except in very close temporalproximity. For example, the part log information 310 for boost pressureis expected to vary rapidly with no intrinsic trend. While for somemeasurement error is still expected, a single reading that falls out ofexpected range by more than some value can indicate a gasket failure,blowoff malfunction, etc. The processing module 504 may evaluate thesemeasurements individually for such characteristics. According to anotherembodiment the processing module 504 may evaluate the part loginformation 310 for boost pressure relative to a continuous functionderived from other contemporaneous readings such as throttle, enginespeed, gear ratio, etc. Yet according to another embodiment, theprocessing module 504 may identify sequences or combinations ofindividually-valid values that are recognized as aberrant when evaluatedtogether (e.g., correlation of simultaneous or sequential signals vs.covariance models). For an example of a sequence of values that might berecognized as aberrant, consider a leaf spring capable of reporting theapparent load on the spring as determined by the degree of deformation.Values may range freely between some well-known extremes, but areexpected to maintain a constant average given a constant load. While thevehicle 104 is in motion, deflections in the spring should return (viadamped motion) to a reasonable and stable center-point. If an extreme(but normal) inflection returns to a stable center significantlydifferent than the center prior to the inflection, it may be anindication that a crack in the leaf spring has reduced the ability ofthe spring to hold a load. For an example of a sequence of values thatmight be recognized as aberrant, when correlated to other values,consider deflection/compression measurements as reported by brakecalipers. If a hydraulic line is faulty, one caliper may experienceconsiderably less deflection than the opposed caliper, even though bothdeflection measurements are individually within tolerance. Similarly,various signals could be correlated with those from related smartcomponents 102, with engine speed, etc. . . . . In one embodiment, theprocessing module 504 may identify the lack or unexpected rate ofappearance of an expected signal. For example, if a previously-recordedsensor 108 fails to report a signal altogether, the processing module504 may determine the part 106 has failed catastrophically, but may moreplausibly be a signal that the sensor 108 itself has failed, or the part106 was replaced.

At decision operation 748, the processing module 504 may compare theanomalies in the part log information 310 with threshold information 712in the part maintenance information 710, as described above, to identifywhether any thresholds have been exceeded. If a threshold is exceeded,then processing continues at operation 750. Otherwise, processingcontinues at operation 752. In another embodiment, the processing module504 may branch to operation 750 based on an identification of one ormore anomalies without making a comparison with the thresholdinformation 712. At operation 750, the processing module 504, mayregister threshold(s) that have been exceeded. In another embodiment,the processing module 504 may register one or more anomalies that wereidentified notwithstanding the threshold information 712.

At operation 752, the processing module 504, may register the servicelevel (e.g., “OK,” “SUGGEST,” “WARN,” “REPLACE”) for the part 106 in theservice level information 318. For example, the processing module 504may generate the service level based on identifying the one or morethresholds that were registered as exceeded in operations 744 and 750.In one embodiment, the processing module 504 may identify the servicelevel based on one or more thresholds that have been exceeded asregistered in operation 744 and/or based on the identification anomalouspart log information 310.

At operation 754, the processing module 504 may send a triggering eventto the smart component engine 505. For example, the processing module504 may send the maintenance message triggering event to the smartcomponent engine 505. In one embodiment, the maintenance messagetriggering event may include the maintenance message 400. The method 728ends.

FIG. 7H illustrates a method 756 to utilize smart components, accordingto an embodiment. The method 756 may commence at operation 758, at thenetwork-based marketplace 118, with the smart component engine 505receiving a triggering event. At operation 758, the smart componentengine 505 may associate the triggering event with processing rules, asdescribed further in this document, and load the processing rules in thesmart component engine 505. At operation 760, the smart component engine505 may execute the processing rules.

FIG. 7I illustrates a user interface 764, according to an embodiment.The user interface 764 is illustrated as being displayed on a mobiledevice 112 (e.g., Apple iPhone). The user interface 764 includes thestring, “Smart Components Application” indicating the name of an “app”that is displaying the user interface 764. For example, the “SmartComponents Application” may embody the maintenance application 200illustrated in FIG. 1 to execute any of the methods described in thisdocument. According to one embodiment, the “Smart ComponentsApplication” “app” may be loaded from the “app store” provided by Apple,Inc. of Cupertino, Calif. The user interface 764 may include a vehiclepart scan user interface element 766, a sub-system part scan userinterface element 768, a part scan user interface element 770, and aconfigure alerts user interface element 772. The vehicle part scan userinterface element 766 may be selected to scan all smart components 102on one or more a vehicles 104 included within a geographic circle wherethe center of the circle is identified as the location of the mobiledevice 112 and the radius of the circle is a predetermined lengthmeasured from the location of the mobile device 112. In one embodiment,the radius is configurable. According to one embodiment, the range of asignal for a smart component 102 (not shown) may be a determining factor(e.g., sending or receiving signal). However, a third party (e.g., thevehicle 104 or shop environment) could conceivably provide area-effect‘power’ for the sensors 108 (e.g., via inductive or RF wireless powertransmission) upon instigation by a triggering signal originating in themobile device 112. In these scenarios, the range of the signal may beconfigurable based upon the power of the output signal, strength of thereturn signal, sensitivity of the receiver, or a selection of which ofthe localized third-party power transmitters were activated. Thesub-system part scan user interface element 768 may be selected to scana sub-system (e.g., smart components 102 in an engine, chassis,electrical, trunk, etc.) that is identified by the user and includedwithin a geographic circle, as previously described. The part scan userinterface element 770 may be selected to scan a part type that isidentified by the user and included within a geographic circle, aspreviously described. It will be observed that proximity-based scans(e.g., vehicle part scan user interface element 766, sub-system partscan user interface element 768, or part scan user interface element770) may pick up parts 106 from neighboring vehicles 104. According toone embodiment, the system 100 (as shown in FIG. 1) may eliminate falsepositives from nearby vehicles 104 by correlating smart components 102identified in multiple scans varied in time & location, and then‘recognizing’ only those smart components 102 that have beenconsistently identified across multiple scans for a particular vehicle104.

The configure alerts user interface element 772 may be selected to entera set of user interfaces that enable configuring of thresholdinformation 712 (e.g., threshold) and maintenance policy information 714for a particular part type, as identified by the network-basedmarketplace 118 with a part type identifier 308, and vehicle 104, asidentified by the network-based marketplace 118 with vehicleidentification information 302. In one embodiment, the thresholdinformation 712 may be configured to enable the dynamic calculation of athreshold responsive to receiving characterization information 312.

FIG. 7J illustrates a user interface 774, according to an embodiment.The user interface 774 is illustrated as being displayed on a mobiledevice 112 (e.g., Apple iPhone). The user interface 774 displays astring, “Engine Part Scan” indicating the results of a sub-system partscan. The user interface 774 may include a user interface element 780,column titles 782 for a “Part,” “Wear,” “Sensor Enabled,” and “ServiceLevel. The user interface 774 may further include rows 784 of partinformation, one for each part 106. The user interface element 780 maybe selected to display a wire diagram including the results of a vehicle104 that was scanned, as illustrated in FIG. 7L. The “Part columndisplays the name that is associated with the part identifier 306 and/orpart type identifier 308 for the part 106. The name of the part 106 isfurther associated with a user interface element “SEARCH” that may beselected to initiate a search for listings 600 that respectivelydescribe an offering of the part 106 for sale or auction on thenetwork-based marketplace 118. The “Wear” column displays a percentagewear as indicated by the most recent characterization information 312for the part 106 or an average of a window of recent characterizationinformation 312 for the part 106. The “Sensor Enabled” column displays“YES” for a smart component 102 with its sensor 108 enabled and “NO” fora smart component 102 with its sensor 108 disabled (e.g., not working,turned off, etc.). The “Service Level” column indicates the currentservice level information 318 (e.g., “OK,” “SUGGEST,” “WARN,” or“REPLACE”) and an estimated replace time based on the location of mobiledevice 112, as previously described. For each row 784, the part 106 isassociated with an indication whether the part 106 was authenticated(e.g., “AUTHENTICATED”) or not authenticated (e.g.,“NOT-AUTHENTICATED”), as previously described.

FIG. 7K illustrates a user interface 786, according to an embodiment.The user interface 786 is illustrated as being displayed on a mobiledevice 112 (e.g., Apple iPhone). The user interface 786 includes userinterface elements 788 and 790 respectively representing smartcomponents 102. The user interface element 788 represents a smartcomponent 102 including a courtesy light bulb part 106 and the userinterface element 790 represents a smart component 102 including anignition switch part 106. Recall, the smart components 102 are eachassociated with a part type identifier 308. The user interface elements(e.g., “HISTORY,” “EXPERTS,” or “MANUALS”) may be selected inconjunction with a selection of one of the user interface elements 788or 790 to display the selected type of information. For example, theuser interface element for “HISTORY” may be selected after selecting theuser interface elements 788 or 790 to display the maintenance historyinformation 316 for the smart component 102 that was selected.Similarly, the user interface element “EXPERT” may be selected afterselecting the user interface elements 788 or 790 to identify an expertfor the part 106 included in the respective smart component 102 and/orenter a chat room that includes the identified expert and/or initiate acommunication with the identified expert. For example, the expert may beidentified based on the part type identifier 308 for the part 106 andthe expert information 220, as shown on FIG. 7C, in the user table 700,as shown on FIG. 7A. The user interface element, “MANUAL,” may beselected after selecting the user interface elements 788 or 790 toidentify a manual to replace the smart component 102 that was selected.In one embodiment, the manual may be identified based an expertise level(e.g., novice, casual fixer, expert) of the user associated with themobile device 112.

Systems and Methods to Utilize an Electronic Garage Shelf

FIG. 8A illustrates a system 800 to utilize an electronic garage shelf,according to an embodiment. The electronic garage shelf may be ametaphor for a shelf in a garage that is used to store parts 106. Merelyfor example, the electronic garage shelf may store token parts thatrespectively represent parts 106 or smart components 102 including oilfilters, carburetors, spark plugs, and fuses that are stored on a garageshelf in the user's garage. Further, the metaphor for a shelf in thegarage may be expanded to include virtual parts that represent parts 106or smart components 102 of interest to the user. Accordingly, the system800 may include garage shelf information 802 comprising virtual partinformation 804 and token part information 806. The virtual partinformation 804 may store virtual parts signifying parts 106 that aredesirable for acquisition and the token part information 806 may storetoken parts signifying parts 106 that are in the user's possession.

Broadly, the system 800 may include: “A”) a set of commands to add,delete, and configure the virtual parts and token parts; “B”) processingto create virtual parts; “C”) processing of the virtual parts; and “D”)processing of the token parts. Processing to create virtual parts mayinclude alerting a particular user to create a virtual part. Forexample, an alert to create a virtual part may be sent to a user who hasexpressed interest in a part 106/smart component 102 by searching forthe part 106. Further for example, an alert to create a virtual part maybe sent to a user for a smart component 102 that reports excessive wear.Processing virtual parts may be proactive or reactive. Processing thatis proactive may include alerting a particular user of a purchaseopportunity related to the virtual part, community content related tothe virtual part, and creating a token part based on the virtual part toprompt the acquisition of the part 106 or smart component 102.Processing that is reactive may include modifying dynamically selectedcontent based on a virtual part. For example, the virtual parts for aparticular user may be input to a mechanism that dynamically selects andranks content. For example, a search mechanism executing a search onbehalf of a user is configured to receive virtual parts as input toselect and rank listings that are returned in a search result to theuser. Further, for example, an automatically invoked merchandisingmechanism (e.g., shopping cart being displayed) is configured to receivevirtual parts as input to select and rank listings that are merchandisedin association with the shopping cart to the user. In both instances auser's implicit interest in a part 106 is accommodated by utilizing thecorresponding virtual part. Processing token parts may be proactive orreactive. Processing token parts that is proactive may include alertinga particular user of a sales opportunity to sell the part 106 or smartcomponent 102 signified by the token part, alerting a particular user ofcommunity content related to the token part, alerting a particular userof installation of the part 106 or smart component 102 signified by thetoken part, and alerting a particular user of deleting the token part.Processing of token parts that is reactive may include evaluatingwhether token parts are compatible with a vehicle 104 that is added to agarage that is associated with a user. For example, a vehicle 104 may beadded to vehicle garage information 706 (not shown) that is associatedwith a user and responsive to the addition of the vehicle 104 ananalysis is performed to identify whether any of the token parts arecompatible with the vehicle (e.g., for repair). For example, a tokenpart that is identified as compatible signifies a part 106 in the realworld that is suitable to replace the corresponding part 106 and/orsmart component 102 in the vehicle 104.

The system 800 may operate in conjunction with smart components 102 aspreviously described with respect to the system 100 in FIG. 1.Accordingly, the same or similar references have been used to indicatethe same or similar features unless otherwise indicated. While thevehicle 104 is illustrated as an automobile, it will be appreciated thattrucks, all-terrain vehicles, jeeps, aircraft, water-born vessels, spacevessels, and the like may embody the illustrated vehicle 104. Merely forexample, a smart component 102 in a Ford Mustang may include a sensor108 for a brake pad that senses information 312 and communicates thecharacterization information 312 over the network 110 (e.g., NFC) to aniPhone that, in turn, communicates a maintenance message 400 includingthe characterization information 312 and a timestamp 314 to thenetwork-based marketplace 118 that, in turn, stores the characterizationinformation 312 and the timestamp 314 in garage information 706 for theFord Mustang in user profile information 702 associated with a user andprocesses the characterization information 312 to identify a “REPLACE”service level for the brake-pad. Responsive to identifying a servicelevel for the brake pad that is not “OK” (e.g., “REPLACE”), thenetwork-based marketplace 118 may communicate an alert to the mobiledevice 112 or the client machine 120 to create a virtual part for thebrake pad. The user may respond by entering a command to create avirtual part for the brake pad in the virtual part information 804.Next, the network-based marketplace 118 may process the virtual part forthe brake pad in the virtual part information 804 to identify a purchaseopportunity on the network-based marketplace 118. For example, anelectronic storefront may be advertising a sale on the brake pad and theuser may be alerted of the sale. Next, the user may purchase the brakepad and enter a command to change the virtual part that was previouslycreated into a token part signifying acquisition the brake pad. In someembodiments, the virtual part may be changed automatically by thenetwork-based marketplace 115. For example, in one embodiment, thenetwork-based marketplace 118 change the virtual part to the token partresponsive to identifying the purchase as concluding an onlinetransaction that was initiated with a search based on the virtual part.Further for example, in one embodiment, the network-based marketplace118 may change the virtual part to the token part responsive toidentifying the purchase as concluding an online transaction that wasinitiated with a search based on an alert that described the virtualpart. Next, the network-based marketplace 118 may process the virtualpart for the brake pad in the garage shelf information 802 tocommunicate an alert to the user to prompt the user to install the brakepad as the corresponding smart component 102 for the break pad is nowreporting 99% wear. Further details and features are described below.

FIG. 8B illustrates the network-based marketplace 118, according to anembodiment. The network-based marketplace 118 may include smartcomponent modules 500 and the database 204. The network-basedmarketplace 118, smart component modules 500 and database 204 operate aspreviously described and as follows. The smart component modules 500 mayinclude a receiving module 502 and a processing module 504 and a smartcomponent engine 505. The receiving module 502 may receive the commandsfrom the mobile device 112 or the client machine 120 and the processingmodule 504 may process the commands to update the database 204. Further,the processing module 504 may communicate responses to the commands,periodically identify and communicate alerts to create virtual parts,process the virtual parts and process the token parts. The processingmodule 504 may process the virtual parts to communicate alerts andperform other operations and process the token parts to communicatealerts and to perform other operations, both as described below. In someinstances, the processing module 504 may further generate a triggeringevent and communicate the triggering event to the smart component engine505 for further processing although other processes on the network-basedmarketplace 118 may generate and communicate a triggering event to thesmart component engine 505. The database 204 may include the garageshelf information 802 and community content information 803 in additionto the other data structures previously described in this documentthough not presently shown. The community content information 803 mayinclude bulletin, recalls, service manuals, installation guides, pricingguides, recommendations, and any other community sourced content thatmay be used to maintain, fix, repair, price, acquire, evaluate, etc. apart 106 or smart component 102, sub-system 103, vehicle 104 or fleet ofvehicles, etc.

FIG. 8C illustrates a user table 700 including the garage shelfinformation 802, according to an embodiment. The garage shelfinformation 802 is stored in the garage information 706 that, in turn,is stored in user profile information 702 that, in turn, is stored inthe user table 700. The garage shelf information 802 may include virtualpart information 804 and token part information 806, as previouslydescribed. The garage shelf information 802 may further include timeoutinformation 807 and garage processing information 809. The timeoutinformation 807 may include three timeouts including a timeout toprocess an alert to create a virtual part, a timeout to process virtualparts and a timeout to process token parts. Responsive to an expirationof one of the timeouts a corresponding method is executed. For exampleresponsive to the expiration of a timeout to process an alert to createa virtual part a corresponding method is executed, as described below.Responsive to an expiration of a timeout to process virtual parts acorresponding method is executed, as described below and responsive toan expiration of a timeout to process token parts a corresponding methodis executed, as described below. The garage processing information 809may include trigger event information 811 that defines triggeringevents, process rules information 815 that stores multiple sets ofprocessing rules, and associate information 817 to associate eachtriggering event to one or more sets of processing rules. The garageprocessing information 809 may be utilized by the smart component engine505 to associate a triggering event with one or more sets of processingrules based on the associate information 817, load the one or more setsof processing rules into the smart component engine 505 and execute theone or more sets of processing rules.

Search Triggering Event—The trigger event information 811 may includethe “search triggering event.” The “search triggering event” may becommunicated by a search mechanism including a search algorithm to thesmart component engine 505. The “search triggering event” may becommunicated responsive to an execution of a search by a user associatedwith the garage shelf information 802. For example, the network-basedmarketplace may receive a request for search that is initiated byselecting a virtual part or a token part that is registered in garageshelf information 802 associated with the user. Responsive to a searchthat is initiated by selecting a virtual part, the smart componentengine 505 may utilize the associate information 817 to associate the“search triggering event” with “get virtual parts process rules” andretrieve the “get virtual parts process rules” from the process rulesinformation 815. Responsive to a search that is initiated by selecting atoken part, the smart component engine 505 may utilize the associateinformation 817 to associate the “search triggering event” with “gettoken parts processing rules” and retrieve the “get token partsprocessing rules” from the process rules information 815. The smartcomponent engine 505 may execute the “get virtual parts processingrules” to identify the virtual parts in the virtual part informationassociated with the user and communicate a list of the virtual parts tothe search algorithm that, in turn, selects and ranks listings 600 basedon the contents of the list and other factors. The smart componentengine 505 may execute the “get token parts processing rules” toidentify the token parts in the token part information 806 associatedwith the user and communicate a list of the token parts to the searchalgorithm that, in turn, selects and ranks listings 600 based on thecontents of the list and other factors. The search algorithm includesthe selected listings 600 in search results that are communicated to theuser.

Merchandise Triggering Event—The trigger event information 811 mayinclude the “merchandise triggering event.” The “merchandise triggeringevent” may be communicated by a merchandising algorithm to the smartcomponent engine 505 responsive to a user performing a predeterminedactivity that suggests the user is receptive to a suggestion (e.g.,making a purchase, browsing for a predetermined period of time,searching for a predetermined period of time, etc.) regardingmerchandise (e.g., an item described by a listing 600). Themerchandising algorithm may select content in the form of listings 600that describe items to merchandise to the user. Responsive to receivingthe “merchandise triggering event,” the smart component engine 505 mayutilize the associate information 817 to associate the “merchandisetriggering event” with “get virtual parts process rules,” retrieve the“get virtual parts processing rules” from the process rules information815, associate the “merchandise triggering event” with “get token partsprocessing rules” and retrieve the “get token parts processing rules”from the process rules information 81. The smart component engine 505may execute the “get virtual parts processing rules” to identify thevirtual parts in the virtual part information associated with the userbased on the interest of the user matching a virtual part interestprofile associated with a virtual part. The smart component engine 505may execute the “get token parts processing rules” to identify the tokenparts in the token part information associated with the user based onthe expressed interest of the user matching a token part interestprofile associated with a token part. The smart component engine 505 mayexecute the “get virtual parts processing rules” based on the expressedinterest of the user to identify a list of virtual parts and communicatethe list of virtual parts to the merchandising algorithm. The smartcomponent engine 505 may execute the “get token parts processing rules”based on the expressed interest of the user to identify a list of tokenparts and communicate the list of token parts to the merchandisingalgorithm. The merchandising algorithm may receive one or both of thelists and process the respective lists to select and rank the listings600 based on the contents of the list(s), in addition to other factors.The merchandising algorithm may merchandise one or more of the selectedlistings 600 to the user based on the ranking.

Completed Transaction Triggering Event

The trigger event information 811 may include the “completed transactiontriggering event.” The “completed transaction triggering event” may becommunicated by a transaction mechanism including a transactionalgorithm to the smart component engine 505. The “completed transactiontriggering event” may be communicated to the smart component engine 505responsive to a user completing a transaction (e.g., payment for anitem) for an item that was initiated based on a virtual part. Forexample, the user may initiate a search for listings 600 based on avirtual part by selecting the virtual part in an alert that iscommunicated to the user. Responsive to receiving the “completedtransaction triggering event,” the smart component engine 505 mayutilize the associate information 817 to associate the “completedtransaction triggering event” with “completed transaction processingrules” and retrieve the “completed transaction processing rules” fromthe process rules information 815. The smart component engine 505 mayexecute the “completed transaction processing rules” to change thevirtual part to a token part. For example, the smart component engine505 may execute the “completed transaction processing rules” to changethe virtual part that was utilized to initiate the transaction to atoken part.

Vehicle Registration Triggering Event

The trigger event information 811 may include the “vehicle registrationtriggering event.” The “vehicle registration triggering event” may becommunicated by the processing module 504 to the smart component engine505 responsive to vehicle information 300 being registered in the garageinformation 706, as previously described. Recall that registration ofvehicle information 300 in association with the user signifies aphysical possession of a vehicle 104 associated with the user.Responsive to receiving the “vehicle registration triggering event,” thesmart component engine 505 may utilize the associate information 817 toassociate the “vehicle registration triggering event” with “alertcompatible parts processing rules” and retrieve the “alert compatibletoken parts processing rules” from the process rules information 815.The smart component engine 505 may execute the “alert compatible partsprocessing rules” to identify token parts in the token part information806 that are compatible with the vehicle 104 that is being registeredand, responsive to the identification, communicate an alert to the userthat includes a message that indicates possession of a part 106 that iscompatible with the vehicle 104. For example, the part 106 that isidentified as compatible with the vehicle 104 may be utilized to fix thevehicle 104.

Vehicle Registration Spare Parts Triggering Event

The trigger event information 811 may include the “vehicle registrationspare parts triggering event.” The “vehicle registration spare partstriggering event” may be communicated by the processing module 504 tothe smart component engine 505 responsive to vehicle information 300being registered in the garage information 706 as spare parts. Forexample, the user may intend to cannibalize the vehicle 104 to use/andor sell its parts 106 and indicate as much in the registration of thevehicle 104 on the network-based marketplace 118. Responsive to receiptof the “vehicle registration spare parts triggering event,” the smartcomponent engine 505 may associate the “vehicle registration spare partstriggering event” with “generate virtual parts for vehicle processingrules.” The smart component engine 505 may execute the “generate virtualparts processing rules” to identify the parts 106 included in thevehicle 104 based on the community content information 803 and generatevirtual parts 814 for all of the parts 106 identified for the registeredvehicle 104.

Search Virtual Part—Sale Triggering Event

The trigger event information 811 may include the “search virtualpart—sale triggering event.” The “search virtual part—sale triggering”event may be communicated by a sales algorithm to the smart componentengine 505 responsive to a sales algorithm identifying a purchase of anitem as concluding an online transaction that was initiated with asearch for a virtual part. For example, a user may execute a “Search VPcommand” (described later) to identify one or more matching virtualparts in the garage shelf information 802 on the network-basedmarketplace 118, select a particular virtual part from the searchresults, contact the user (e.g., owner), and purchase the correspondingpart 106 or win the part 106 in an auction. Recall the virtual partsignifies a part 106 that may be acquired from the user associated withthe garage shelf information that includes the virtual part. Responsiveto receiving the “search virtual part—sale triggering event,” the smartcomponent engine 505 may utilize the associate information 817 toassociate the “search virtual part—sale triggering event” with “changevirtual part processing rules” and retrieve the “change virtual partprocessing rules” from the process rules information 815. The smartcomponent engine 505 may execute the “change virtual part processingrules” to change the virtual part corresponding to the part 106 that waspurchased to a token part. For example, the smart component engine 505may execute “Change VP to TP” command, as described later, to change thevirtual part to a token part.

Bar Code Scan Triggering Event

The trigger event information 811 may include the “bar code scantriggering event.” The “bar code scan triggering event” may becommunicated by the smart component engine 505 responsive to a userscanning a bar code on a part 106 and identifying the part 106 based onthe bar code. Responsive to receiving the “bar code scan triggeringevent,” the smart component engine 505 may utilize the associateinformation 817 to associate the “bar code scan triggering event” with“change virtual part processing rules” and retrieve the “change virtualpart processing rules” from the process rules information 815. The smartcomponent engine 505 may execute the “change virtual part processingrules” to identify a virtual part that corresponds to the scanned part106 and change the virtual part to a token part. For example, the smartcomponent engine may execute “Change VP to TP” command, as describedlater, to change the virtual part to a token part.

FIG. 8D illustrates a table 808 of garage shelf commands, according toan embodiment. The table 808 includes an “add virtual part command,” a“delete virtual part command,” a “configure virtual part command,” an“add token part command,” a “delete token part command,” a “configuretoken part command,” a “change virtual part to token part command,” a“search virtual part command,” and a “search token part command.”

The “add virtual part command” may be utilized to add a virtual part tothe virtual part information 804. The “add virtual part command” mayreceive input parameters including a vehicle identifier (e.g., year,make, model, vehicle identification number, etc.), a part typeidentifier 308 (e.g., oil filter), and a part identifier 306 (e.g.,unique identifier or range of unique identifiers) and process the inputparameters to add an a virtual part to the virtual part virtual partinformation 804 in the garage shelf information 802 associated with theuser who entered the command.

The “delete virtual part command” may be utilized to delete a virtualpart from the virtual part information 804 in the garage shelfinformation 802 associated with the user who entered the command. The“delete virtual part command” may receive an input parameter including avirtual part identifier and process the virtual part identifier todelete the identified virtual part.

The “configure virtual part command” may receive input parametersincluding a virtual part identifier and other parameters and process theinput parameters to configure the virtual part in the garage shelfinformation 802 associated with the user who entered the command. Forexample, the virtual part information 804 may include user-preferredbrands, YES/NO alert configuration settings, and a timeout period toprocess the virtual part.

The “add token part command” may receive input parameters including avehicle identifier (e.g., year, make, model, vehicle identificationnumber, etc.), a part type identifier 308 (e.g., oil filter), and a partidentifier 306 (e.g., unique identifier or range of unique identifiers)and process the input parameters to add one token part to the token partinformation 806 in the garage shelf information 802 associated with theuser who entered the command.

The “delete token part command” may be utilized to delete a token partfrom the token part information 806 in the garage shelf information 802associated with the user who entered the command. The “delete token partcommand” may receive a token part identifier and be process the tokenpart identifier to delete the identified token part.

The “configure token part command” may receive input parametersincluding a token part identifier and other parameters and process theinput parameters to configure the token part in the token partinformation 806 in the garage shelf information 802 of the user whoentered the command. For example, the token part information 806 mayinclude user-preferred brands, YES/NO alert configuration settings, anda timeout period to process the token part.

The “change virtual part to token part command” may receive a virtualpart identifier and change the identified virtual part to a token part.According to one embodiment, the “change virtual part to token partcommand” may be automatically executed responsive to scanning a bar codeor part identifier on a part 106 or smart component 102, as previouslydescribed. For example, a user may utilize their mobile device 112 toscan a part identifier on a part 106 or smart component 102 andcommunicate a message to the network-based marketplace 118 that, inturn, causes the smart component modules 500 to receive the message,identify a virtual part with a matching part identifier 306 or part typeidentifier 308 and responsive to the identification, communicate the“bar code can triggering event” to the smart component engine 505 tochange the virtual part to a corresponding token part.

The “search virtual part command” may be utilized to identify a virtualpart in the virtual part information 804 in the garage shelf information802. For example, the “search virtual part command” may receive inputparameters including a part type identifier 308 or part identifier 306or some other search criteria (e.g., alphanumeric string) and processthe input parameters to search all of the virtual part information 804in the network-based marketplace 118. For example, a user may want tomake an offer to another user to sell a part 106 to a user who isassociated with a corresponding virtual part.

The “search token part command” may be utilized to identify a token partin garage shelf information 802. For example, the “search token partcommand” may receive input parameters including a part type identifier308 or part identifier 306 or some other search criteria (e.g.,alphanumeric string) and process the input parameters to search all ofthe token part information 806 in the network-based marketplace 118. Forexample, a user may want to make an offer to another user to purchase apart 106 a part from user who is associated with a corresponding tokenpart.

In one embodiment, a virtual part or token part may be utilized tosearch the items table 506 for matching listings 600. For example, theinput parameter for the search may include a virtual part or a tokenpart. In one embodiment, the search parameters may further include avehicle 104 to limit the scope of the search to the vehicle 104. Forexample, that input parameters may specify one more elements of thevehicle information 300 including the make, model and year of thevehicle. In one embodiment, the input parameters may further include abrand preference that describe brands and other preferences that limitthe scope of the search to the brands and other preferences. Forexample, the search parameters may include one or more elements of userpreference information 704 including a brand preference.

In one embodiment, a virtual part or token part may be utilized tosearch the items table 506 for compatible listings 600. For example, acompatible listing 600 may describe an item that is compatible with thevirtual part or the token part. For example, an item that is compatiblemay be an accessory to the virtual part or the token part. Further, anitem that is compatible may be assembled with the virtual part or tokenpart. Further, an item that is compatible may be inserted into thevirtual part or token part. Further, an item that is compatible may becontained by the virtual part or token part.

FIG. 8E illustrates virtual part information 804, according to anembodiment. The virtual part information 804 may store one or morevirtual parts 812. The virtual parts 812 may be created with the “addvirtual part command” and deleted with the “delete virtual partcommand.”

FIG. 8F illustrates a virtual part 812, according to an embodiment. Thevirtual part 812 may include vehicle identification information 302, aspreviously described; a part identifier 306, as previously described; apart type identifier 308, as previously described; virtual partpreference information 813 and other content for describing,illustrating or imaging the virtual part 812. The virtual partpreference information 813 may store user-preferred brands and otherpreferences, as configured by the user.

FIG. 8G illustrates token part information 806, according to anembodiment. The token part information 806 may store one or more tokenparts 814. The token parts 814 may be created with the “add token partcommand” and the “change virtual part to token part command.” The tokenparts 814 may further be deleted with the “delete token part command.”

FIG. 8H illustrates a token part 814, according to an embodiment. Thetoken part 814 may include vehicle identification information 302, aspreviously described; a part identifier 306, as previously described; apart type identifier 308, as previously described, token part preferenceinformation 816 and other content for describing, illustrating orimaging the token part 814. The token part preference information 816may store user-preferred brands and other preferences, as configured bythe user.

FIG. 8I illustrates a method 818 to process commands, according to anembodiment. The method 818 describes processing commands for controllingthe electronic garage including the commands in table 808, as shown inFIG. 8D. The method 818 may commence, at operation 820, with thereceiving module 502 receiving the command and its corresponding inputparameters. Merely for example, a user may enter the input parametersinto an input box on the mobile device 112 or the client machine 120. Inanother embodiment, the receiving module 502 may utilize a menu-driveninterface to interact with the user operating the mobile device 112 toreceive the command and input parameters. At operation 822, theprocessing module 504 may process the command. For example, theprocessing module 504 may process the commands related to a virtual partto store user-preferred brands, YES/NO alert configuration settings, anda timeout period. Further for example, the processing module 504 mayprocess the commands related to a token part to store user-preferredbrands, YES/NO alert configuration settings, and a timeout period.

FIG. 8J illustrates a method 821 to alert a creation of a virtual part,according to an embodiment. The method 821 commences, at operation 823,for a particular user on the network-based marketplace 118 responsive tothe expiration of a timeout for the method 821 in the timeoutinformation 807 in garage shelf information 802 associated with theuser. The timeout may be configured to periodically expire (e.g., onceper day) by the user or an administrator.

At decision operation 823, the processing module 504 may identifywhether the user has expressed an interest in one or more parts 106. Forexample, the user may express an interest in a part 106 by searching forthe part 106, browsing to the part 106, or watching the part 106. If theuser has expressed interest then a branch is made to operation 825.Otherwise the processing module 504 branches to operation 827. Atoperation 825, the processing module 504 may communicate an alert to theuser to create a virtual part 812. For example, the alert may include amessage indicating that the user expressed interest in a part 106 orsmart component 102 and a question asking the user whether they wouldlike to create a virtual part 812 that corresponds to the part 106 orsmart component 102.

At operation 827, the processing module 504 may advance to the firstentry of vehicle information 300 (e.g., vehicle 104) in the garageinformation 707 in the user profile information 702. At operation 829,the processing module 504 may advance to the first entry of partdescription information 304 (e.g., smart component 102) for theparticular vehicle 104.

At decision operation 831, the processing module 504 may identifywhether the smart component 102 has a service level that is not “OK.”For example, the processing module 504 may identify service levelinformation 318 that includes a service level that is “SUGGEST,” “WARN”,or “REPLACE.” If the service level is “OK,” then the processing module504 branches to decision operation 835. Otherwise the processing module504 branches to operation 833.

At operation 833, the processing module 504 may communicate an alert tothe user including a message to create a virtual part 812 correspondingto the identified smart component 102 in the vehicle 104 associated withthe user. For example, the alert may include a question that asks theuser whether they would like to create a virtual part 812 based on theidentified smart component 102. In some embodiments, the alert mayfurther include the service level for the smart component 102 and awarning that is appropriate for the service level, as previouslydescribed.

At decision operation 835, the processing module 504 identifies whethermore part description information 304 in the current vehicle information300 is to be processed. If more part description information 304 is tobe processed then the processing module 504 advances to the next partdescription information 304 in the current vehicle information 300 andthen branches to decision operation 831. Otherwise the processing module504 branches to decision operation 837.

At decision operation 837, the processing module 504 may identifywhether more vehicle information 300 (e.g., for a vehicle 104) in thegarage information 706 that is associated with the current user is to beprocessed. If more vehicle information 300 is to be processed then theprocessing module 504 advances to the next vehicle information 300 inthe garage information 706 and then branches to operation 829. Otherwisethe processing module 504 branches to operation 839. At operation 839,the processing module 504 sets the timeout for the method 821 in thetimeout information 807. For example the processing module 504 sets thetimeout for the method 821 in the timeout information 807 in garageshelf information 802 associated with the particular user on thenetwork-based marketplace 118.

FIG. 8K illustrates a method 824 to process virtual parts, according toan embodiment. The method 824 commences, at operation 826, responsive tothe expiration of a timeout for the method 824 in the timeoutinformation 807 in garage shelf information 802 associated with aparticular user on the network-based marketplace 118. The timeout may beconfigured (e.g., once a day) by the user with the “configure virtualpart command.” At operation 826, the processing module 504 may advanceto the first virtual part 812 in the virtual part information 804 in thegarage information 706 associated with the user.

At decision operation 828, the processing module 504 may identifywhether an alert is configured for purchase opportunities. For example,an alert may be configured “YES” by the user with the “configure virtualpart command.” If the alert is configured “YES,” then processingcontinues at operation 830. Otherwise processing continues at decisionoperation 832. At operation 830, the processing module 504 may identifywhether any purchase opportunities are available based on the currentvirtual part 812. For example, the processing module 504 may execute asearch of the items table 506 utilizing information in the currentvirtual part 812 including the part identifier 306 and/or the part typeidentifier 308 and/or virtual part preference information (e.g.,favorite brands, style, discounted items, etc.) and communicate an alertto the current user responsive to identifying one or more listings 600that match. For example, the processing module 504 may communicate analert that includes links to the listings 600 describing items beingoffered for sale that match the current virtual part 812. Further, forexample, the processing module 504 may execute a search of token partinformation 806 on the network-based marketplace 118 utilizinginformation in the current virtual part 812 including the partidentifier 306 and/or the part type identifier 308 and/or virtual partpreference information (e.g., favorite brands, style, discounted items,etc.) and communicate an alert to the current user responsive toidentifying one or more listings 600 that match. For example, theprocessing module 504 may communicate an alert that includes links tothe token parts 814 describing items being offered for sale that matchthe current virtual part 812 and the identity of the users respectivelyassociated with the token parts 814. Other embodiments of the alert donot disclose the identity of the users. Further for example, the alertmay include links that invoke a search for compatible listings 600 onthe network-based marketplace 118. Compatible listings 600 describe anitem that is related to the virtual part 812. For example, the item maybe an accessory to the virtual part 812 or an element that is assembledwith the virtual part 812 or an element that is inserted into thevirtual part 812.

At decision operation 832, the processing module 504 may identifywhether an alert is configured for community content. For example, thealert may be configured “YES” by the user with the “configure virtualpart command.” If the alert is configured “YES,” then processingcontinues at operation 834. Otherwise processing continues at decisionoperation 836. At operation 834, the processing module 504 may identifywhether new community content is available based on the current virtualpart 812 and, if so, communicate an alert to the user. For example, theprocessing module 504 may execute a search of the community contentinformation 803 utilizing information in the current virtual part 812including the part identifier 306 and/or the part type identifier 308and/or virtual part preference information (e.g., favorite brands,style, discounted items, etc.) and communicate an alert to the userresponsive to identifying one or more new elements of community contentinformation 803 that match. Further for example, the processing module504 may communicate an alert including links to the elements ofcommunity content information 803 (e.g., installation guide).

At decision operation 836, the processing module 504 may identifywhether an alert is configured to alert the creation of a token part 814based on the current virtual part 812. For example, the alert may beconfigured “YES” by the user with the “configure virtual part command.”If the alert is configured “YES,” then processing continues at decisionoperation 838. Otherwise processing continues at decision operation 842.At decision operation 838, the processing module 504 may identifywhether the current virtual part 812 corresponds to a smart component102 that is registered in the user's garage information 706. Forexample, the processing module 504 may identify the smart component 102by respectively matching the vehicle identification information 302 inthe virtual part 812 with the vehicle identification information 302 inany of the entries of vehicle information 300 in the same user profileinformation 702 and further respectively matching the part typeidentifier 308 and the part identifier 306 in the virtual part 812 withthe part type identifier 308 and the part identifier 306 in any of theentries of part description information 304 in the identified vehicleinformation 300. In some embodiments, a fuzzy match may be sufficient toregister a match (e.g., part identifier 306 is not included to registera match, a range of part identifiers 306 sufficient to register a match,a range of vehicle identification information 302 is sufficient toregister a match, or any combination thereof). At decision operation839, the processing module 504 may identify whether the service levelinformation 318 includes a service level for the identified smartcomponent 102 that is registered as “OK.” If the service levelinformation 318 for the identified smart component 102 is registered as“OK” then processing continues at decision operation 842. Otherwiseprocessing continues at operation 840 (e.g., service level is “SUGGEST,”“WARN”, or “REPLACE”). At operation 840, the processing module 504 maycommunicate an alert to the user to create a token part 814 based on thecurrent virtual part 812. Recall that the token part 814 is a proxy foractual possession of the part 106. Accordingly, the alert provides anotice to the user to acquire the part 106 because the correspondingsmart component 102 in a vehicle 104 has a service level that registersnot “OK.” In some embodiments, the alert may include the service levelof the identified smart component 102.

At decision operation 842, the processing module 504 may identifywhether more virtual parts 812 are in the virtual part information 804.If more virtual parts 812 are included in the virtual part information804 then processing continues at operation 850. Otherwise the processingmodule 504 branches to operation 844. At operation 850, the processingmodule 504 advances to the next virtual part 812 and then continuesprocessing at decision operation 828. At operation 844, the processingmodule 504 sets the timeout that, upon expiration, initiates the method824 for the user. For example the processing module 504 sets the timeoutfor the method 824 in the timeout information 807 in garage shelfinformation 802 associated with the particular user on the network-basedmarketplace 118.

FIG. 8L illustrates a method 860 to process token parts, according to anembodiment. The method 860 commences at operation 862 responsive to theexpiration of a timeout for the method 860 in the timeout information807 in garage shelf information 802 associated with a particular user onthe network-based marketplace 118. The timeout may be configured (e.g.,once a day) by the user with the “configure token part command.” Atoperation 862, the processing module 504 may advance to the first tokenpart 814 in the token part information 806 in the garage information 706associated with the user.

At decision operation 864, the processing module 504 may identifywhether an alert is configured for sales opportunities. For example, thealert may be configured “YES” by the user with the “configure token partcommand.” If the alert is configured “YES,” then processing continues atoperation 866. Otherwise processing continues at decision operation 868.At operation 866, the processing module 504 may communicate an alertindicating a part 106 that corresponds to the present virtual part 812is being offered for sale. For example, the processing module 504 maycommunicate the alert to users on the network-based marketplace 118 whoare looking for the part 106 that corresponds to the current token part814 (e.g., operation 830 on FIG. 8K, users who are “watching” for thepart 106, etc.).

At decision operation 868, the processing module 504 may identifywhether an alert is configured for community content. For example, thealert may be configured “YES” by the user with the “configure token partcommand.” If the alert is configured “YES,” then processing continues atoperation 870. Otherwise processing continues at decision operation 872.At operation 870, the processing module 504 may identify whether newcommunity content is available based on the current token part 814 and,if so, communicate an alert to the user. For example, the processingmodule 504 may execute a search of the community content information 803utilizing information in the current token part 814 including thevehicle identification information 302, the part identifier 306 and/orthe part type identifier 308 and/or virtual part preference information(e.g., favorite brands, style, discounted items, etc.) and communicatean alert to the user responsive to identifying one or more new elementsof community content information 803 that match. For example, theprocessing module 504 may communicate an alert that includes one or morelinks to elements of community content information 803 (e.g.,installation guide).

At decision operation 872, the processing module 504 may identifywhether an alert is configured to replace a smart component 102 in avehicle 104. For example, the alert may be configured “YES” by the userwith the “configure token part command.” Recall that the current tokenpart 814 is a proxy for a real part 106 or smart component 102 on ashelf in the user's garage. If the alert is configured “YES,” thenprocessing continues at decision operation 873. Otherwise processingcontinues at decision operation 876.

At decision operation 873, the processing module 504 may identifywhether the current token part 814 corresponds to a smart component 102that is registered in user's garage information 706. For example, theprocessing module 504 may identify a smart component 102 in user'sgarage information 706 by matching the vehicle identificationinformation 302, the part type identifier 308 and/or the part identifier306 of the current token part 814 with the respective information in asmart component 102 that is registered in user's garage information 706.In some embodiments, a fuzzy match may be sufficient to register a match(e.g., part identifier 306 is not included to register a match, a rangeof part identifiers 306 is sufficient to register a match, a range ofvehicle identification information 302 is sufficient to register amatch, or any combination thereof). At decision operation 874, theprocessing module 504 may identify whether the service level information318 for the smart component 102 includes a service level that isregistered as “OK.” If the service level for the identified smartcomponent 102 is registered “OK” then processing continues at decisionoperation 876 and the user is not alerted. Otherwise processingcontinues at operation 875 (e.g., service level is “SUGGEST,” “WARN”, or“REPLACE”) and the user is alerted. At operation 875, the processingmodule 504 may communicate an alert to the user to replace the smartcomponent 102 with the part 106 or smart component 102 corresponding tothe current token part 814. In some embodiments, the alert may includethe service level.

At decision operation 876, the processing module 504 may identifywhether to alert the user to remove the current token part 814. Forexample, the processing module 504 may identify a smart component 102that is being reported by a vehicle 104 that is registered with vehicleinformation 300 in the garage information 706 for the user with a partidentifier 306 that matches the part identifier of the current tokenpart 814. If the processing module 504 identifies a match thenprocessing continues at operation 878. Otherwise processing continues atdecision operation 880. At operation 878, the processing module 504 maycommunicate an alert to the user to delete the current token part 814.In some embodiments, the current token part 814 may be automaticallydeleted responsive to receiving a maintenance message or some othermessage reporting a matching vehicle identification information 302,part type identifier 308 and part identifier 306.

At decision operation 880, the processing module 504 may identifywhether more token parts 814 are in the token part information 806. Ifthe token part information 806 includes more token parts 814, thenprocessing continues at operation 882. Otherwise processing continues atoperation 844. At operation 882, the processing module 504 advances tothe next token part 814 and processing continues at decision operation864. At operation 884, the processing module 504 sets the timeout that,upon expiration, initiates the method 860. For example the processingmodule 504 sets the timeout for the method 860 in the timeoutinformation 807 in garage shelf information 802 associated with theparticular user on the network-based marketplace 118.

FIG. 8M illustrates a method 885 to utilize an electronic garage shelf,according to an embodiment. The method 885 may commence at operation 886with the receiving module 502, at the network-based marketplace 118,receiving a maintenance message 400, as described in operation 730 inFIG. 7G. The maintenance message 400 is communicated by the mobiledevice 112 to the network-based marketplace 118 responsive the mobiledevice 112 receiving characterization information 312 from a smartcomponent 102 that operates in a vehicle 104. For example, the smartcomponent 102 may include a sensor 108 that senses the wear of a brakepad that provides braking for the front left wheel of a 1999 FordExplorer.

At operation 888, the processing module 504 may identify user profileinformation 702 (e.g., John Doe) in a user table 700 based on a useridentifier 218 in the maintenance message 400, as described in operation732 in FIG. 7G.

At operation 890, the processing module 504 may store thecharacterization information 312 and the timestamp 314 for the brakepad, as part log information 310, in the appropriate part descriptioninformation 304 (e.g., part 106—brake pad) in the appropriate vehicleinformation 300 (e.g., vehicle 104-199 Ford Explorer) in the garageinformation 706 (e.g., garage) in the user profile information 702(e.g., user—John Doe), as described in operation 734 in FIG. 7G.

At operation 892, the processing module 504 may register a service levelfor the smart component 102 in the vehicle 104, as described inoperations 740-752 in FIG. 7G. For example, the processing module 504may register a service level of “REPLACE” for the brake pad.

At operation 894, the processing module 504 may communicate an alert tothe user (e.g., John Doe) to create a virtual part 812, as described inoperations 831 and 833 in FIG. 8J. For example, the processing module504 may communicate an alert to create a virtual part 812 for the brakepad responsive to identifying a service level that is not “OK” (e.g.,“REPLACE”).

At operation 896, the receiving module 502 may receive an “add virtualpart” command for the brake pad from the user, as described in operation820 in FIG. 8I. Further at operation 896, the processing module 504 mayadd the virtual part 812 to the virtual part information 804 in thegarage information 706 of the user profile information 702 of the user,as described in operation 822 in FIG. 8I.

FIG. 8N illustrates a user interface 898, according to an embodiment.The user interface 774 is one example of the “add a virtual part”command.

Systems and Methods for Multi-Signal Automated Fault Analysis

FIG. 9A illustrates a system 900, according to an embodiment, formulti-signal fault analysis. The system 900 may include a collectiondevice 901 that utilizes a network 110 to collect multiple signals froma vehicle 104, communicate the signals, over a network 116 to anetwork-based marketplace 118 that, in turn, stores the multiple signalsas multi-signal information 902, analyzes the multi-signal information902 to identify a diagnosis of the fault and communicates the diagnosisback over the network 116 to one of the mobile devices 112 or a clientmachine 120. The collection device 901 may be comprised of one or moremobile devices 112. The collection device 901 may further be configuredusing one of the mobile devices 112 or the client machine 120. Eachmobile device 112 may be utilized to sense one or more physicalphenomena and communicate signal messages including signal informationthat represents the physical phenomena, over the network 116, to thenetwork-based marketplace 118. The sensed phenomena, at the mobiledevice 112, may include optical phenomena, motion phenomena, orientationphenomena, geolocation phenomena, temperature phenomena, humidityphenomena, weather phenomena including atmospheric pressure phenomena,and any other physical phenomena that are representable as signalinformation. Further, each mobile device 112 may be used to receivecharacterization information 312 from one or more smart components 102in the vehicle 104 and communicate the characterization information 312(e.g., signal information) in a signal message, over the network 116, tothe network-based marketplace 118, as previously described. Accordingly,a single mobile device 112 may be configured to sense and communicateone or more types of physical phenomena that are sensed by the mobiledevice 112 and/or relay one or more types of characterizationinformation 312 that are sensed by smart components 102 that communicatethe characterization information 312 to the mobile device 112. Thesignal information may be stored at the network-based marketplace 118 asmulti-signal information 902 according to channels that respectivelycorrespond to the mobile devices 112 and sub-channels that are utilizedto distinguish different streams of signal information at the samemobile device 112. The network-based marketplace 118 may analyze themulti-signal information 902 to identify a correlated event that isdefined in the fault analysis repository 904 as one or more sets ofsignal information or derived characteristics that, when combinedtogether, characterize a diagnosis. For example, a squeaking sound and asmart component 102 reporting 90% brake wear that are both received assignal information within five seconds of applying brakes in a 1967 FordMustang are received and analyzed as multi-signal information 902 toidentify a correlated event corresponding to a diagnosis of a brakefailure. Further, the network-based marketplace 118 may associate thediagnosis with a prognosis to facilitate a repair of the identifiedfault. It will be appreciated by one skilled in the art that the system900 may operate in conjunction with smart components 102, as describedin this document. Accordingly, the same or similar references have beenused to indicate the same or similar features unless otherwiseindicated. While the vehicle 104 is illustrated as an automobile, itwill be appreciated that trucks, all-terrain vehicles, jeeps, aircraft,water-born vessels, space vessels, and the like may embody theillustrated vehicle 104. Further, one skilled will appreciate that aruggedized form of multi-signal fault analysis may be performed onentities other than the vehicle 104 and in environments that are deemedtoo difficult to access (e.g., desert, mountain, cliff, top of astructure, etc.) or too hazardous to access (e.g., military/combat). Forexample, in an environment where direct human placement of the mobiledevices 112 is too hazardous, one or more mobile devices 112 may bemounted on one or more drones, configured as a collection device 901,and flown into the hazardous environment to collect signal informationfrom the test object. Accordingly, the collection device 901 may beflown to a recently destroyed bridge in a combat zone to collect signalinformation in an otherwise too hazardous environment. Further forexample, in an environment where direct human placement of the mobiledevices 112 is too difficult to access, one or more mobile devices 112may be mounted on one or more drones, configured as a collection device901, and flown to the difficult to access environment to collect signalinformation from the test object. For example, the collection device 901may be flown to a turbine in a wind tower to collect signal informationin an otherwise too hazardous environment.

In a more typical example, a user may perform a fault analysis on a 1967Ford Mustang by configuring the collection device 901 to collect(operation “A′”) signal information from a first mobile device 112 thatreceives signal information from a smart component 102 that includes asensor 108 that senses a brake pad that is mounted on the front rightwheel of the Mustang and signal information from a second mobile device112 that includes a microphone that receives audio. Further, the usermay operate wearable technology such as an optical head-mounted receiverand display (e.g., Google Glass) that may be tapped by the user to armthe collection device 901 to monitor for receipt of signalinginformation for the squeaking sound to initiate the capture and storageof multi-signal information 902 including the above described audiosignal information and signal information from a smart component 102.For a particular test, the user follows test design informationincluding instructions to rest the second mobile device 112 on apassenger seat of the Mustang, accelerate to a speed of five mph, tap onthe Google Glass to arm the collection device 901, and apply the brakesto achieve a dead stop. Accordingly, the network-based marketplace 118may respond to the tap on the Google Glass by monitoring the signalmessage information from the second mobile device for receipt of thesqueaking sound and responsive to receipt of the squeaking sound store(operation “B′”) multiple instances of the signal message informationfrom the first and second mobile devices. Further, the network-basedmarketplace 118 may respond to an end of the test event by initiating ananalysis (operation “C′”) of the multi-signal information 902 that wascollected to diagnose (operation “D′”) the fault (e.g., right frontbrake is worn out) and communicate a message including the diagnosis ofthe fault to the first mobile device. In some embodiments, the messagemay further include a prognosis (operation “E′”) including an estimatedcost for repair at a local service shop and a list of parts.

The collection device 901 may be comprised of one or more mobile devices112 including mobile devices 112 that are carried (e.g., smart phonesand other devices that are carried), mobile devices 112 that are worn(e.g., smart glasses, smart watches, and other smart devices that areworn), and mobile devices 112 that are purpose built. The mobile devices112 that are purpose built are now further described. Mobile devices 112that are purpose built are designed for a particular purpose andlocation. Mobile devices 112 that are purpose built may be designed toinclude a magnetic attachment or fastener attachment for attachment totarget location (e.g., engine compartment, wheel well, etc.). Mobiledevices 112 that are purpose built may provide in-operation monitoringfrom the target locations that not accessible to a human-held orconsumer-grade device. Mobile devices 112 that are purpose built may bedifferent in appearance from a consumer device (e.g., no display,ruggedized exterior, hermetically sealed, etc. . . . ), nevertheless,implement the same functions as other mobile devices 112 that operate inthe collection device 901. For example, mobile devices 112 that arepurpose built may operate as general-purpose single or multi-channelsignal devices. Further, mobile devices 112 that are purpose built mayoperate to capture one or more specific types of signals and/or inspecific use cases (e.g., including a monitor designed to diagnoseengine noise with an optional rigid temperature resistant modulecontaining only noise/vibration sensors 108) (e.g., including a monitordesigned to diagnose engine noise with an optional rigid temperatureresistant module containing only an adhesive single-use temperature andflexion monitor) (e.g., including a monitor designed to capture belttiming via a strobe & camera).

FIG. 9B illustrates a test protocol 906, according to an embodiment.Illustrated on the left are operations performed by one or more mobiledevices 112 and illustrated on the right are operations performed by thenetwork-based marketplace 118. The test protocol 906 may includecommunications originating from the mobile devices 112 including theuser test request information 908 and fault analysis test session 912and a communication originating from the network-based marketplace 118including the test design information 910.

The user test request information 908 may include a request for a faultanalysis. For example, the user test request information 908 may includeinformation typically communicated to a mechanic who is skilled infixing vehicles 104 including symptoms, sounds, failures, conditions,etc. Responsive to receipt of the user test request information 908, thenetwork-based marketplace 118 may match the user test requestinformation 908 to corresponding system test request information in thefault analysis repository 904 (not shown) to identify the appropriatetest design information 910 and communicate the test design information910 back to the mobile device 112.

The test design information 910 may include instructions to configurethe collection device 901, instructions to establish conditions forperforming the data collection (e.g., drive at a specific speed andapply brakes), and instructions to arm the collection device 901 (e.g.,tap on the Google Glass) to collect signal information. For example, theuser may follow the instructions in the test design information 910 toregister mobile devices 112 and the type of signal information beingreceived by each of the mobile devices 112 with one or more commandsthat are entered from the mobile device 112. Further for example, theuser may follow the instructions in the test design information 910 toregister a wearable device by pairing the wearable device (e.g., GoogleGlass, smart watch, etc.) with a particular mobile device 112.

The fault analysis test session 912 is comprised of a test arming event914, a test triggering event 916, multi-signal information 902, and atest end event 918. The test arming event 914 may be received from oneof the mobile devices 112 as signal information to signal thenetwork-based marketplace 118 to begin monitoring signal information fora test triggering event 916. For example, the test arming event 914 maybe a tap on Google Glass. The test triggering event 916 may further bereceived as signal information to signal the network-based marketplace118 to begin collecting and storing the multi-signal information 902.For example, the test triggering event 916 may be a squeaking sound thatis sensed after the test arming event 914 has been received. In somecases, the test design information 910 may describe the test armingevent 914 and the test triggering event 916 as the same event. The testend event 918 may be received as signal information or a system timeoutthat signals to the network-based marketplace 118 that the faultanalysis test session 912 has completed and to begin an analysis of themulti-signal information 902 that was collected. For example, responsiveto receipt of the test end event 918, the network-based marketplace 118may register the end of the fault analysis test session 912 and analyzethe multi-signal information 902 to identify whether the faultidentified with the user test request information 908 was diagnosed. Thenetwork-based marketplace 118 may analyze the multi-signal information902 by comparing it with the multi-signal information 902 in the faultanalysis repository 904 to identify a one or more correlated events.Identification of one or more correlated events constitutes a diagnosisof the problem. On the other hand, if the problem is not diagnosed, thefault analysis test session 912 may be repeated with a new set of testdesign information 910. For example, the network-based marketplace 118may alter the test conditions or add a new mobile device 112 to collectadditional signal information or add more signal information (e.g.,speed, sound, image, motion picture, etc.) to an existing mobile device112. The process described above may be iterated until the problem isdiagnosed or until all available tests are exhausted. In someembodiments, the network-based marketplace 118 may request expert manualintervention in response to identifying all available tests isexhausted.

FIG. 9C illustrates a network-based marketplace 118, according to anembodiment. The network-based marketplace 118 may include smartcomponent modules 500 and a database 204. The network-based marketplace118, smart component modules 500 and database 204 operate as previouslydescribed and further as follows. The smart component modules 500 mayinclude a receiving module 502 and a processing module 504. Thereceiving module 502 may receive commands from the mobile device 112 orthe client machine 120. Further, the receiving module 502 may receivethe user test request information 908 (not shown), events included inthe fault analysis test session 912 (not shown) and the signalingmessages from the mobile devices 112 (not shown) including signalinformation that is collectively stored as multi-signal information 902(not shown) in the appropriate user profile information 702. Theprocessing module 504 may process the aforementioned information,events, and messages including the signal information to update thedatabase 204, and respond to the mobile devices 112 and client machine120. The database 204 may include the user profile information 702 inthe user table 700 and fault analysis repository 904 in addition toother data structures previously described though not presently shown.The user profile information 702 may be used to store the multi-signalinformation 902 for one or more fault analysis according to users on thenetwork-based marketplace 118. The fault analysis repository 904 may beused to store multiple entries of system fault analysis information 953that are used to diagnose the problems/faults described by the userfault analysis information 920.

FIG. 9D illustrates user profile information 702, according to anembodiment. The user profile information 702 has been previouslydescribed. With respect to the current feature, the user profileinformation 702 may store one or more entries of user fault analysisinformation 920 for a particular user on the network-based marketplace118. For example, each fault analysis that is initiated by a user withthe user test request information 908 may be associated with one entryof user fault analysis information 920.

FIG. 9E illustrates a fault analysis repository 904, according to anembodiment. The fault analysis repository 904 may be used to storesystem fault analysis information 953 entries that are used forfault/problem diagnosis. For example, multiple system fault analysisinformation 953 entries may be stored in the fault analysis repository904 for diagnosing a front brake failure for a 1967 Ford Mustang andother types of failures. Accordingly, a user fault analysis information920 entry in the user profile information 702 that is being utilized toperform a fault analysis for a particular user may be compared withrelevant entries of system fault analysis information 953 in the faultanalysis repository 904 to identify and communicate test designinformation 910, diagnose a fault, identify a prognosis of a fault andidentify one or more experts. Accordingly, each of the system faultanalysis information 953 entries may be considered signatures for aparticular problem diagnosis, as described further below. The faultanalysis repository 904 may be generated based on different sources ofinformation. For example, an entry of system fault analysis information953 may be generated based on a bulletin or a recall notice. Accordingto one embodiment, an entry of system fault analysis information 953that is generated based on a bulletin or a recall notice may be utilizedto confirm or pre-qualify a particular vehicle 104 as exhibitingsymptoms associated with the bulletin or recall.

FIG. 9F illustrates user fault analysis information 920, according to anembodiment. The user fault analysis information 920 may include usertest request information 908 and test session information 922. The usertest request information 908 may be received from the user or thenetwork-based marketplace 118 and stored in the user fault analysisinformation 920. Receipt of user test request information 908 initiatesa fault analysis. The user test request information 908 in the userfault analysis information 920 may be compared with the system testrequest information in system fault analysis information 953 to identifya match. Responsive to identification of the match, the test designinformation 910 and other information from the system fault analysisinformation 953 may be utilized to perform a fault analysis, asdescribed further below. The test session information 922 includes oneor more entries of multi-signal information 902 that are collected withthe collection device 901. Each entry of multi-signal information 902corresponds to one fault analysis test session 912.

FIG. 9FF illustrates user test request information 908, according to anembodiment. The user test request information 908 may be received from auser or from the network-based marketplace 118 to initiate multi-signalfault analysis. For example, a user may interact with a set of userinterfaces to make selections that are utilized to generate the usertest request information 908 for storage in the user fault analysisinformation 920 in the user profile information 702. Further, forexample, the network-based marketplace 118 may automatically generatethe user test request information 908 based on a recall or servicebulletin that identifies a part 106 and vehicle 104, the user testrequest information 908 being communicated to a mobile device 112 that,in turn, receives an affirmation from the user that is communicated withthe user test request information 908 back to the network-basedmarketplace 118 to initiate multi-signal fault analysis for a particularvehicle 104. In another embodiment, the processing module 504 mayautomatically generate the user test request information 908 responsiveto receiving characterization information 312 from smart component 102that is stored in part description information 304 (e.g., part 106)associated with a user. For example, responsive to receipt ofcharacterization information 312, the processing module 504 may identifythe characterization information 312 for the particular part 106 andvehicle 104 as being associated with a particular type of user testrequest information 908 by performing a mapping operation (e.g.,identifying an predetermined association between (part 106, vehicle 104,identified characterization information 312) and the user test requestinformation 908), communicating the user test request information 908 toa mobile device 112 that, in turn, receives an affirmation from the userthat is communicated with the user test request information 908 back tothe network-based marketplace 118 to initiate multi-signal faultanalysis for a particular vehicle 104. In another embodiment, the usertest request information 908 may be communicated directly to thenetwork-based marketplace 118 to initiate multi-signal fault analysisand a notice of test initiation may be communicated to the user. Inanother embodiment, the processing module 504 may automatically generatethe user test request information 908 responsive to identifying a levelof service in service level information 318 in part descriptioninformation 304 (e.g., part 106) associated with a user. For example,responsive to identification of service level information 318 that isnot “OK,” the processing module 504 may identify the identification of aservice level in service level information 318 that is not “OK” for theparticular part 106 and vehicle 104 as being associated with aparticular type of user test request information 908 by performing amapping operation (e.g., identifying an predetermined associationbetween (part 106, vehicle 104, identified service level information318) and the user test request information 908), communicating the usertest request information 908 to a mobile device 112 that, in turn,receives an affirmation from the user that is communicated with the usertest request information 908 back to the network-based marketplace 118to initiate multi-signal fault analysis for a particular vehicle 104. Inanother embodiment, the user test request information 908 may becommunicated directly to the network-based marketplace 118 to initiatemulti-signal fault analysis and a notice of test initiation may becommunicated to the user.

The user test request information 908 may include problem conditions934, problem symptoms 936 and vehicle identification information 302.The problem conditions 934 may describe conditions that are associatedwith the problem symptoms 936. For example, the problem conditions 934may include a particular range of speed and/or motion such as turningright, turning left, backing up, etc. The problem symptoms 936 mayinclude some discretely observable phenomena such as a high pitchedsound, a low rumbling sound, a loss of power, a vibration, etc. thatoccurs in association with the problem conditions 934. The vehicleidentification information 302 describes a make, model, and year of avehicle 104, as previously described. All or part of the vehicleidentification information 302 may be optionally entered.

FIG. 9G illustrates system fault analysis information 953, according toan embodiment. The system fault analysis information 953 may be utilizedto identify and communicate test design information 910 and analyze thetest session information 922 in the user fault analysis information 920(not shown) to diagnose a fault. The system fault analysis information953 may include the system test request information 955, test designinformation 910, correlation information 924, diagnosis information 926,prognosis information 928, and expert identifier information 930. Thesystem test request information 955 may be utilized to associate aparticular entry of system fault analysis information 953 with user testrequest information 908 to initiate a fault analysis test session 912(not shown). The test design information 910 was previously described.The correlation information 924 may be utilized to analyze themulti-signal information 902 in the user fault analysis information 920(not shown). The diagnosis information 926 may include diagnosticproblem information, diagnostic repair information and diagnosticcertainty information. The diagnostic problem information includes adiagnosis of the problem described by the associated system test requestinformation 955. For example, the diagnostic problem information mayinclude “front left tire is low on air,” “spark plug in number 4cylinder is misfiring,” “engine is running roughly,” “battery low.” Thediagnostic repair information may include a remedy to the diagnosedproblem such as “replace front left tire,” “replace spark plug in numberfour cylinder,” “perform tune-up,” “replace battery.” The diagnosticcertainty information may include a quantified certainty that thediagnosis of the problem is correct. For example, the diagnosticcertainty information may include 90%. The prognosis information 928 mayinclude information related to fixing the fault that is diagnosed. Forexample, the prognosis information 928 may include repair estimateinformation and repair list information. The repair estimate informationmay be utilized to generate estimates for repair based on a userperforming their own work or based on a local shop performing the work.The repair estimate information utilized to generate estimates forrepair based on a local shop performing the work may include a monetaryestimate to fix the vehicle 104, an estimate of time to perform thework, a likelihood that the repair will address the problem (e.g., apercentage), and an estimate of urgency to fix the problem including alevel of risk (e.g., YELLOW, ORANGE, or RED) or a cascading failuredescription describing other failures likely to occur if the currentproblem is not fixed. The repair list information may be utilized togenerate a list of parts that are needed to repair the problem describedby the associated user test request information 908. The list mayfurther include an estimated cost for each of the parts from a supplier.The expert identifier information 930 may include user identifiers 218that identify users on the network-based marketplace 118 that arequalified experts to diagnose or fix the problem described by theassociated system test request information 955.

FIG. 9GG illustrates system test request information 955, according toan embodiment. The system test request information 955 may beinitialized by a system administrator. The system test requestinformation 955 may include problem conditions 934, problem symptoms 936and vehicle identification information 302, as previously described. Thesystem test request information 955 may be compared with user testrequest information 908 to identify a match. A fuzzy match mayconstitute a match. For example, overlapping ranges of problemconditions 934 and/or overlapping ranges of problem symptoms 936 and/oroverlapping ranges of vehicle identification information 302 or parts ofthe vehicle identification information 302 may constitute a match.

FIG. 9H illustrates test design information 910, according to anembodiment. The test design information 910 may include test collectioninformation 938, test condition information 940, test arming information942, test triggering information 944 and test end information 946.Recall that the test design information 910 is communicated to a userresponsive to receiving from the user the user test request information908 that includes a description of a problem with a vehicle 104. Thetest design information 910 provides instructions for the user toperform a fault analysis test session 912 (not shown). The testcollection information 938 may provide specifications for configuringthe collection device 901. For example, the test collection information938 may specify the number of mobile devices 112 and the type ofsignaling information that is collected at each of the mobile devices112. Further, the test collection information 938 may specify whetherone or more wearable devices are included in the collection device 901and other information related to the wearable devices including the typeof signaling information to collect and the identity of the mobiledevice 112 to pair with the wearable device. Further the test collectioninformation 938 may instruct the user to perform multiple fault analysistest sessions 912 as prompted by the network-based marketplace 118 witha notice that includes a reminder. For example, the network-basedmarketplace 118 may communicate a notice to the user including areminder for the user to perform the next multiple fault analysis testsession 912. In one embodiment, the network-based marketplace 118 maycommunicate the notice for the next fault analysis test session 912based on a schedule (e.g., date and time). In one embodiment, thenetwork-based marketplace 118 may communicate the notice for the nextfault analysis test sessions 912 to be performed based on thenetwork-based marketplace 118 identifying one or more conditions (e.g.,time and/or date and/or presence in the car and/or driving condition)that maximize the value of the fault analysis test sessions 912. Thetest condition information 940 may specify the conditions under which toperform the fault analysis test session 912. For example, the testcondition information 940 may specify the position (e.g., on thedashboard, under the hood, back seat, front seat, etc.) of the mobiledevice(s) 112, the driving activities (e.g., speed, motion, activity,etc.), and the driving conditions (e.g., rain, snow, up a hill, down ahill, etc.) for the fault analysis test session 912. The test arminginformation 942 may specify a test arming event 914 that is received bya mobile device 112 or wearable device to arm the collection device 901.For example, the test arming event 914 may include a tap, a push of abutton, a waving motion, or some other signal that is sensed. The testtriggering information 944 may specify a test triggering event 916 thatis received by a mobile device 112 to initiate collection and storage ofsignal information. For example, the test triggering event 916 mayinclude signaling information for a discrete phenomenon that is receivedas signal information by one of the mobile devices 112 in the collectiondevice 901. For example, the test triggering event 916 may include oneof the problem symptoms 936 included in the user test requestinformation 908. The test end information 946 may specify a test endevent 918 that terminates the fault analysis test session 912. Forexample, the test end event 918 may include a timeout that expires aperiod of time after the test triggering event 916 is received. Furtherfor example, the test end event 918 may include a discrete phenomenonthat is received as signal information by one of the mobile devices 112in the collection device 901.

FIG. 9I illustrates multi-signal information 902, according to anembodiment. The multi-signal information 902 may include channelinformation 950, event information 952, sub-channels 954, and signalinformation 856. All channel information 950 in the multi-signalinformation 902 is associated with a single collection device 901 andfault analysis test session 912. Each entry of channel information 950is associated a mobile device 112 that may receive one or more entriesof signal information 956 respectively identified according tosub-channels 954. Two sub-channels 954 are illustrated on the left asassociated with one channel information 950 (e.g., channel zero),however, more or fewer sub-channels 954 may be configured. The signalinformation 956 may be received from a mobile device 112 in signalmessages and stored in the multi-signal information 902 in chronologicalorder according to the timestamps 314. The signal information 956 isillustrated as being received with earlier timestamps 314 towards thetop. Signal information 965 may be compressed without loss, compressedwith acceptable loss with acceptable lossiness as defined by a systemadministrator or user, sparsely represented (e.g., omitting“uninteresting” data leaving resulting signal information 965 that isdiscontinuous according to timestamps 314 and optionally annotated),represented as a processed or derived form (e.g., frequency-domaintransform), annotated as sequence of interpreted events (e.g., [“time1:05: event 85C”, “time 1:10: event 85C” ]), annotated with an indirectreference (e.g., stored signal information 965 is equivalent toreference (or previously-delivered) signal ABC 123 within specifiedtolerances). In addition, the signal information 965 may not beanomalous. In these instances the signal information 965 may beannotated “not anomalous,” “existing,” “no-anomaly,” “provided uponrequest,” “folded,” or “delta.” The “folded” annotation signifies signalinformation 965 is based upon a fixed periodicity where a repeatingsignal is treated as a series of many measurement windows with only theaveraged measurement of one or more windows being reported. The “delta”annotation signifies signal information 965 that is being reported asthe difference of a reference signal (e.g., natural, synthetic, modeled,etc.). The “phase” annotation signifies a shift of one instance ofsignal information 965, in time, relative to another instance of signalinformation 965. The “delta” and “phase” annotations may be used inconjunction. For example, if a sample of signal information 965 isslightly delayed relative to a reference sample of signal information965, and also contains a small amount of ‘interesting’ noise, then thetime shift can be represented by a single phase measurement, with theremaining noise being represented efficiently by delta measurementsbetween the phase-corrected signals.

Each of the signal information 956 is further illustrated asrepresenting different phenomena over time with differentcharacteristics (e.g., hill, little ratchet, big ratchet). The eventinformation 952 may store a registration of the test arming event 914, aregistration of the test triggering event 916, a registration ofcorrelated events (e.g., “'A,” “'B,” “'C”) a registration of the testend event 918, and annotations as described above though not shown. Thecorrelated events are registered, as such, in the event information 952for a fault analysis test session 912 responsive to an analysis thatidentifies a match with correlation information 924 in the faultanalysis repository 904 (not shown), as described further below. A fuzzymatch may be sufficient to constitute a match. For example, thecorrelated event may be registered in the event information 952 in themulti-signal information 902 responsive to correlated events (e.g.,“'A,” “'B,” “'C”) that differ in time, magnitude, periodicity, etc.within respective and specified ranges as specified by correlationinformation 924 in the user fault analysis information 920 in the faultanalysis repository 904.

FIG. 9J illustrates correlation information 924, according to anembodiment. The correlation information 924 may store one or morecorrelated events 958, as previously described. A particular correlatedevent 958 is a signature to diagnose a failure. The correlationinformation 924 may include multiple and different correlated events 958and each correlated event 958 may be sufficient to diagnose the samefailure (e.g., brake failure). Each correlated event 958 may be comparedwith multi-signal information 902 in the user profile information 702 toidentify whether the multi-signal information 902 matches the correlatedevent 958 signifying diagnosis of the failure. For example, thecorrelated event 958 that is presently illustrated is comprised of anevent “'A” that was identified in first signal information 956, an event“'B” that was identified in second signal information 956, and an event“'C” that was identified in third signal information 956 to constitute asingle correlated event 958. Further, the events “'A,” “'B” and “'C” inthe user profile information 702 may be identified to constitute a matchwith the events “'A,” “'B” and “'C” in the correlation information 924according to predetermined ranges of variability in the shape, timing,amplitude, and periodicity of the respective events. Further, the events“'A,” “'B” and “'C” in the user profile information 702 may beidentified to constitute a match with the events “'A,” “'B” and “'C” inthe correlation information 924 according to predetermined ranges ofvariability in relation to each other. For example, a predeterminedrange of variability between event “'A” and “'B” may include theiroccurrence in time within a predetermined range (e.g., two minutes).Further, the number of events in one correlated event 958 may be more orfewer than the number of events in another correlated event 958.

FIG. 9K illustrates a signal message 960, according to first embodiment.The signal message 960 may be communicated by a mobile device 112 to thenetwork-based marketplace 118 responsive the mobile device 112 beingconfigured to sense and report a type of physical phenomena (e.g.,image, motion image, sound, pressure, temperature, etc.) at the mobiledevice 112. The signal message 960 may include a user identifier 218,vehicle identification information 302, channel information 950,sub-channel 954, signal information 956 and the timestamp 314, all aspreviously described.

FIG. 9L illustrates a signal message 960, according to a secondembodiment. The signal message 960 may be communicated by a mobiledevice 112 to the network-based marketplace 118 in response to themobile device 112 being configured to receive characterizationinformation 312 from a smart component 102 and communicate thecharacterization information 312 in the signal message 960 to thenetwork-based marketplace 118. The signal message 960 may include amaintenance message 400, as previously described. The signal message 960may further include channel information 950 and the sub-channel 954 bothas previously described. The characterization information 312 may bereceived as signal information 956 at the network-based marketplace 118.

FIG. 9M illustrates a method 961 to process a test request, according toan embodiment. Illustrated on the left are operations performed at themobile device 112 and illustrated on the right are operations performedat the network-based marketplace 118. The method 961 may commence atoperation 962, at the mobile device 112, with a user entering user testrequest information 908 that is communicated to the network-basedmarketplace 118. For example, the user may navigate a series of screensto generate user test request information 908 including problem symptoms936 describing a squeaking sound emanating from the right front wheelunder problem conditions 934 describing brakes that are applied at aspecified speed for vehicle identification information 302 describing a1967 Ford Mustang with a vehicle identification number of XYZ 123245 andodometer reading of 1234567.

At operation 964, at the network-based marketplace 118, the receivingmodule 502 may receive the user test request information 908 and atdecision operation 966 the processing module 504 may identify whetherthe test design information 910 is identified in the fault analysisrepository 904 for the user test request information 908 that wasreceived. The decision operation 966 is described more fully withreference to FIG. 9O as a method 903 to identify test design information910. If the test design information 910 is identified (e.g., “NEXTTEST”), at decision operation 966, then a branch is made to operation968. Otherwise a branch is made to connector “E” (e.g., “NO TEST”) whichcorresponds to connector “E” on FIG. 9N. At operation 968, theprocessing module 504 may communicate the test design information 910 tothe mobile device 112.

At operation 970, at the mobile device 112, the user may receive thetest design information 910. At operation 972 the user may configure thecollection device 901 based on the test collection information 938 inthe test design information 910. For example, the user may configure afirst mobile device 112 to receive characterization information 312 froma smart component 102 that senses brake wear on the front right brake inthe Mustang, configure a second mobile device 112 to sense audio, andexecute a pairing operation to pair the Google Glass with the secondmobile device 112. At operation 974, the user may setup test conditionsbased on based on the test condition information 940 in the test designinformation 910. For example, the user may set the first mobile device112 and the second mobile device 112 on the passenger's seat in theMustang, accelerate to five mph, tap the Google Glass and apply thebrakes to achieve a dead stop.

FIG. 9N illustrates a method 976 for multi-signal automated faultanalysis, according to an embodiment. Illustrated on the left areoperations performed at the mobile devices 112 and illustrated on theright are operations performed at the network-based marketplace 118. Themethod 976 may commence, at operation 978, with the mobile devices 112in the collection device 901 communicating signal messages 960 to thenetwork-based marketplace 118. According to one embodiment, the mobiledevices 112 may commence communicating signal messages 960 responsive tobeing configured as part of the collection device 901 by the user.According to another embodiment, the mobile devices 112 may commencecommunicating signal messages 960 responsive to receipt of the testarming event 914. For example, the network-based marketplace 118 mayreceive a message from the Google Glass via the paired first mobiledevice 112 and communicate commands to the first mobile device 112 andthe second mobile device 112. For example, the network-based marketplace118 may communicate a command to the first mobile device 112 to enablesignal messages 960 to report characterization information 312 by thesmart component 102 and to the second mobile device 112 to enable signalmessages 960 to report the sensing of audio. According to yet anotherembodiment, the first mobile device 112 may commence communicatingsignal messages 960 responsive to receipt of the tap on the Google Glassand the second mobile device 112 may be enabled to commencecommunicating signal messages 960 responsive to receipt of the testtriggering event 916 (e.g., squeaking sound) at the first mobile device112.

At operation 979, at the network-based marketplace 118, the signalmessages 960 are received by the receiving module 502 and at decisionoperation 980 the processing module 504 processes the signal messages960 to identify a type of signal processing. The decision operation 980is described more fully on FIG. 9P as a method 919 to identify signalprocessing. If the signal information 956 is identified as “NO SIGNAL”then processing ends until another signal message 960 is received. Ifthe signal information 956 is identified as “STORE SIGNAL,” thenprocessing continues at operation 982 and if the signal information 956is identified as “END DATA COLLECTION,” then processing continues atdecision operation 986. At operation 982, the processing module 504 mayidentify user profile information 702 based on the user identifier 218in the signal message 960. At operation 984, the processing module 504may store the signal information 956 from the signal message 960 in theappropriate user fault analysis information 920 in the user profileinformation 702. For example, the processing module 504 may utilize thevehicle identification information 302, channel information 950,sub-channel 954, and timestamp 314 in the signal message 960 to identifythe appropriate location in the user fault analysis information 920 forstorage. Note that the characterization information 312 in theembodiment of the signal message 960 including the maintenance message400 is stored as signal information 956 in the user fault analysisinformation 920.

At decision operation 986 the processing module 504 analyzes themulti-signal information 902 in the user fault analysis information 920based on the current system fault analysis information 953 (e.g.,identified previously with the decision operation 966 in FIG. 9M basedon matching the user test request information 908 with system testrequest information 955) to identify whether the fault is diagnosed. Thedecision operation 986 is illustrated more fully in FIG. 9Q as a method941 to analyze multiple signals. If the multi-signal information 902 isidentified as “DIAGNOSED,” then processing continues at operation 990.If the multi-signal information 902 is identified as “NOT DIAGNOSED”then processing continues at decision operation 994.

At decision operation 994 the processing module 504 may identify whetheradditional test design information 910 is available. The decisionoperation 994 is described more fully in FIG. 9O as a method 903 toidentify test design information 910. If the processing module 504, atdecision operation 994, identifies additional test design information910 is available then a branch is made to connector “F” whichcorresponds to connector “F” on FIG. 9M. Otherwise a branch is made tooperation 996.

At operation 990, the processing module 504 may communicate a messageincluding diagnosis information 926 to the mobile device 112 thatinitiated the fault analysis. In some embodiments, the client machine120 may initiate the fault analysis. For example, the message mayinclude diagnosis information 926 that indicates the front right brakepad needs to be replaced. In another embodiment, the message may furtherinclude prognosis information 928, as previously described. At operation998, the mobile device 112 may display the message including thediagnosis information 926 and/or the prognosis information 928.

At operation 996, the processing module 504 may communicate a notice tothe mobile device that initiated the fault analysis indicating expertassistance has been requested. For example, the processing module 504may identify a qualified expert to assist the user based on the expertidentifier information 930 in the system fault analysis information 953,communicate a request the expert including a request for theirassistance in diagnosing the problem, and communicate a notice to theuser that initiated the test indicating that an expert is expectedcontact the user momentarily to assist the user in diagnosing theproblem. At operation 998, the mobile device 112 may receive and displaythe message including the above described notice.

FIG. 9O illustrates a method 903, according to an embodiment, toidentify test design information 910. The method may receive and utilizeuser test request information 908 and an index, described more fullybelow, to identify test design information 910. The method 903 mayidentify test design information 910 by matching the user test requestinformation 908 with system test request information 955 in an entry ofsystem fault analysis information 953 in the fault analysis repository904. More specifically, the method 903 may be entered multiple times toinitiate multiple fault analysis test sessions 912. Each entry of themethod 903 includes an index that is passed to the method 903 anddesignated by the method 903 as the current system fault analysisinformation 953 (e.g., the place to begin searching the fault analysisrepository 904). The method 903 utilizes the current system faultanalysis information 953 to begin a search for the next entry ofmatching system fault analysis information 953. The method 903 mayreturn “NEXT TEST” and an index corresponding to the identified entry ofsystem fault analysis information 953 responsive to identifying a matchor “NO TEST” responsive to identifying the fault analysis repository 904is exhausted. The method 903 may commence, at operation 905, with theprocessing module 504 receiving an index and designating the index asthe “next system fault analysis information 953. Entry of the method 903from decision operation 966 of FIG. 9M initializes the “next systemfault analysis information” to the first entry of system fault analysisinformation 953. That is, entry of the method 903 from decisionoperation 966 of FIG. 9M is for initiating execution of the first faultanalysis test session 912. Entry of the method 903 from decisionoperation 994 of FIG. 9N is for execution of a successive fault analysistest session 912. Accordingly, the entry of the method 903 from decisionoperation 994 of FIG. 9N initializes the “next system fault analysisinformation” with an index corresponding to the entry of system faultanalysis information 953 following the entry of system fault analysisinformation 953 that was utilized for the previous fault analysis testsession 912. For example, the method 903 may be entered from decisionoperation 994 of FIG. 9N three times to initialize the “next systemfault analysis information” with the twentieth, twenty-fifth, andninetieth entries of the system fault analysis information 953 in thefault analysis repository 904. At decision operation 907, the processingmodule 504 may identify whether vehicles 104 match. For example, theprocessing module 504 may compare vehicle identification information 302in the user fault analysis information 920 in the user profileinformation 702 with vehicle identification information 302 in thecurrent system fault analysis information 953 in the fault analysisrepository 904. If vehicles 104 match, then processing continues atdecision operation 909. Otherwise processing continues at decisionoperation 913. A fuzzy match may constitute a match. For example, anoverlapping range of years and/or overlapping range of makes and/oroverlapping range of models may constitute a match. Further, theentirety of the vehicle identification information 302 may not beutilized for a particular comparison. For example, the vehicleidentification number may not be utilized for a particular comparison.

At decision operation 909, the processing module 504 may identifywhether user test request information 908 matches the current systemtest request information 955. For example, the processing module 504 maycompare user test request information 908 in the user fault analysisinformation 920 in the user profile information 702 with system testrequest information 955 in the current system fault analysis information953 in the fault analysis repository 904. If a match is identified thenprocessing continues at operation 911. Otherwise processing continues atdecision operation 913. A fuzzy match may constitute a match. Forexample, overlapping ranges of problem conditions 934 and/or overlappingranges of problem symptoms 936 may constitute a match. At operation 911,the processing module 504 may return the value “NEXT TEST” to decisionoperation 994 on FIG. 9N or decision operation 966 on FIG. 9M. Themethod 903 would then end.

At decision operation 913, the processing module 504 may identifywhether more entries of system fault analysis information 953 arepresent in the fault analysis repository 904 for processing. If moreentries are available for processing, then a branch is made to operation905. Otherwise processing continues at decision operation 915.

At operation 915, the processing module 504 may communicate a message toan expert requesting their assistance in designing a test to diagnosethe current problem. For example, the processing module 504 may identifythe expert based on the expert identifier information 930 in the currentsystem fault analysis information 953. At operation 917, the processingmodule 504 may return the value “NO TEST” to decision operation 994 ofFIG. 9N or decision operation 966 of FIG. 9M. The method 903 then ends.

FIG. 9P illustrates a method 919, according to an embodiment, toidentify signal processing. The method 919 is entered from decisionoperation 980 on FIG. 9N to process signal information 956 in a signalmessage 960 that was received from a mobile device 112. The method 919commences at decision operation 921 with the processing module 504identifying whether the collection device 901 was previously armed. Ifthe processing module 504 identifies the collection device 901 aspreviously armed then processing continues at decision operation 925.Otherwise processing continues at decision operation 923.

At decision operation 923, the processing module 504 identifies whetherthe signal information 956 in the signal message 960 that is presentlybeing processed includes a test arming event 914. For example, theprocessing module 504 may utilize the test arming information 942 in thetest design information 910 in the current system fault analysisinformation 953 to identify whether the signal message 960 includes thetest arming event 914. If the processing module 504 identifies the testarming event 914 then processing continues at decision operation 925.Otherwise processing continues at operation 935.

At decision operation 925, the processing module 504 identifies whetherthe collection device 901 was previously triggered. If the processingmodule 504 identifies the collection device 901 as previously triggered,then processing continues at decision operation 929. Otherwiseprocessing continues at decision operation 927.

At decision operation 927, the processing module 504 identifies whetherthe signal information 956 in the signal message 960 that is presentlybeing processed includes a test triggering event 916. For example, theprocessing module 504 may utilize the test triggering information 944 inthe test design information 910 in the current system fault analysisinformation 953 to identify whether the signal message 960 includes thetest triggering event 916. If the processing module identifies the testtriggering event 916 then processing continues at operation 933.Otherwise processing continues at operation 935.

At decision operation 929, the processing module 504 identifies whetherthe signal information 956 in the signal message 960 that is presentlybeing processed includes a test end event 918. For example, theprocessing module 504 may utilize the test end information 946 in thetest design information 910 in the current system fault analysisinformation 953 to identify whether the signal message 960 includes thetest end event 918. If the processing module 504 identifies the test endevent 918 then processing continues at operation 931. Otherwiseprocessing continues at operation 933. In some embodiments an expiredtimeout may be utilized to simulate the test end event 918. In otherembodiments, the signal message 960 that is presently being processedmay be combined with an expired timeout to constitute the test end event918.

At operation 931, the processing module 504 may return “END DATACOLLECTION” to decision operation 980 of FIG. 9N. At operation 933, theprocessing module 504 may return “STORE SIGNAL” to decision operation980 of FIG. 9N. At operation 935, the processing module 504 may return“NO SIGNAL” to decision operation 980 of FIG. 9N.

FIG. 9Q illustrates a method 941, according to an embodiment, to analyzemulti-signal information 902. The method 941 is entered from decisionoperation 986 of FIG. 9N to analyze signal information 956 inmulti-signal information 902 in user profile information 702 that wasreceived from a collection device 901. The method 941 commences, atdecision operation 943, with the processing module 504 identifyingwhether the multi-signal information 902 matches at least one correlatedevent 958 in the correlation information 924 of the current system faultanalysis information 953 in the fault analysis repository 904. A fuzzymatch may constitute a match, as previously described. At operation 947,the processing module 504 may return “NOT DIAGNOSED” to decisionoperation 986 on FIG. 9N. At operation 945, the processing module 504may return “DIAGNOSED” to decision operation 986 on FIG. 9N.

FIG. 9R illustrates a user interface 949, according to an embodiment, toconfigure a collection device 901. The user interface 949 illustrates acollection device including four mobile devices 112 respectivelyoperating on channels zero, one, two, and three and respectivelyassociated with different telephone numbers. Channel zero includes twosub-channels including a first sub-channel that captures signalinformation 956 that represents audio phenomena and a second sub-channelthat captures signal information 956 that represents visual phenomena.Other embodiments may include additional sub-channels 954. Channel onecaptures signal information 956 that represents characterizationinformation 312 reported by a smart component 102. Channel two capturessignal information 956 that represents temperature phenomena. Channelthree captures signal information 956 that represents accelerationphenomena. The user interface 949 further illustrates the mobile device112 associated with channel zero as being utilized to configure thecollection device 901. In some embodiments, the same mobile device 112may be paired with one or more mobile devices 112 that are wearable(e.g., Google Glasses, smart watch, etc.). Any of the mobile devices 112may be utilized to capture a test arming event 914 or a test triggeringevent 916.

FIG. 9S illustrates a user interface 951, according to an embodiment, todisplay partial results for a multi-signal automated fault analysisincluding aspects of the diagnosis information 926 and prognosisinformation 928.

Systems and Methods for an E-Commerce Enabled Digital Whiteboard

FIG. 10A illustrates a system 1000, according to an embodiment, for ane-commerce enabled digital whiteboard. The system 1000 is generallydescribed in the present disclosure to process interactions between avehicle owner who is collaborating with other users (e.g., experts) torepair a vehicle 104 (not shown), however, other collaborations mayinclude management personnel who collaborate to plan a budget, engineerswho collaborate to build a software system, publishers who collaborateto identify whether to publish a book, shoppers who collaborate to makea purchase (e.g., online shopping assistance) and the like.

Broadly, the system 1000 may include a network-based marketplace 118that utilizes a context 1002, including a context identifier 1004,initialization information 1008 and request information 1010 to processinteractions between users who are collaborating online, theinteractions being received as requests via a user interface 1012. Forexample, the network-based marketplace 118 may utilize the context 1002to process interactions in an online collaborative workspace 1014 toexpose feature information 1006 and/or augment feature information 1006and/or remove feature information 1006 from the user interface 1012 inaddition to improving the relevancy and/or enabling ecommerce activitiesthat are presented via the user interface 1012.

The network-based marketplace 118 may utilize the context 1002 toprocess interface information. Interface information may includeinformation that is exposed or received via the user interface 1012. Forexample the interface information may include requests/interactions thatare received via the online collaborative workspace 1014. Theinteractions may include manipulating objects including documents,videos, illustrations, wire frame diagrams and the like, hostingreal-time audio/visual online collaborative workspace sessions withother users and the like, and facilitating general drop and dragfacilities for links, objects, etc. and other typical digital whiteboardfacilities and the like. The interface information may further includefeature information 1006. For example, the feature information mayinclude participant information 1016, metadata information 1018, searchinformation 1020, tool information 1022, dialogue information 1024,shopping cart information 1026, context information 1028 including thecontext 1002, advertising information 1033 and promotional information1035. The feature information 1006 may be displayed as interfaceinformation according to panels on the user interface 1012 or asdiscrete user interface elements or as groups of user interface elementson the user interface 1012.

As briefly mentioned above but now discussed, the feature information1006 may be hidden or exposed. For example, the participant information1016 may be added or removed to interact with expert users. Further forexample, the metadata information 1018 may be added or removed tomanipulate objects in a separate workspace. Specifically, the metadatainformation 1018 may be used to manipulate instances of objectspresently displayed on another part of the user interface 1012. Further,the metadata information 1018 may be used to display instantiations ofan archetypical object. For example, the metadata information 1018 maydisplay user interface elements rendering Fram or Napa oil filters forparallel viewing with an archetypical oil filter that is being displayedin a repair schematic in the online collaborative workspace 1014. Thesearch information 1020 may include search results, queries, savedsearches, and other search related information. Further the searchinformation 1020 may be generated based on searches being performed forlistings 600 (not shown) on the network-based marketplace 118. The toolinformation 1022 may include tools to operate the user interface 1012and manipulate the contents of the user interface 1012. The dialogueinformation 1024 may include scripts representing spoken words, typedwords, messaged words, etc. and generally any statement (e.g.,declarative, question, etc.) submitted by any user from present andprevious online collaborative sessions. The shopping cart information1026 may include listings 600 (not shown) and other elements supportingsales and other e-commerce activity including merchandising activities.The context information 1028 may include the context 1002, as previouslydescribed. The advertising information 1033 may include advertisementelements, merchandising elements (e.g., listings) and other elementssupporting sales and other e-commerce activity. The promotionalinformation 1035 may include promotion elements (e.g., discounts, games,etc.), merchandising elements and other elements supporting sales andother e-commerce activity.

More specifically, the system 1000 may include a mobile device 112(e.g., smart phone) operated by a first user who enters an “add context”command (operation “A”) on the mobile device 112 to add the context1002. The mobile device 112 may communicate the context 1002, over anetwork 116, to a network-based marketplace 118 that, in turn, processesthe “add context” command and the context 1002 to store the context 1002in a directory in user profile information 702 that is associated withthe first user on the network-based marketplace 118. Responsive toprocessing the “add context” command, the network-based marketplace 118may communicate a context identifier 1004 back to the mobile device 112.Further, the first user may enter an “attach context” command (operation“8”) and the context identifier 1004 with the mobile device 112 toattach the context 1002 to the online collaborative workspace 1014. Tothis end, the mobile device 112 may communicate the command and thecontext identifier 1004, over the network 116, to the network-basedmarketplace 118 that, in turn, processes the command and the contextidentifier 1004 to attach the context 1002 to the online collaborativeworkspace 1014, generate the user interface 1012 by utilizing thecontext 1002 and communicate the user interface 1012, back over thenetwork 116, to the mobile device 112. Further, one or more other userswho are remotely located to the user may enter a request by touch oranother activity that is received via the one or more instances of the,touch sensitive, user interface 1012. The network-based marketplace 118may receive the requests, process the requests based on the context 1002including the initialization information 1008 and all of the requestinformation 1010 including the present and previous requests. Responsiveto processing the requests, the network-based marketplace 118 may(re)generate the user interface 1012 or parts of the user interface 1012and communicate the user interface 1012 or parts thereof back over thenetwork 116 to the one or more mobile devices 112.

In one example, the initialization information 1008 may include adescription of vehicle 104 (not shown) and a description of a repair forthe vehicle. For example, the initialization information 1008 maydescribe a 1967 Ford Mustang that needs a repair in the form of an oilfilter replacement. Continuing with the example, the context 1002 may beattached to the online collaborative workspace 1014, as previouslydescribed, and the online collaborative workspace 1014 may be generatedbased on the initialization information 1008 in the context 1002 toinclude a repair schematic for replacing the oil filter. Subsequent todisplaying the repair schematic, requests may be received from thefirst, second, and other users, who are collaborating to replace the oilfilter, and stored in the context 1002 as request information 1010. Forexample, the requests may include a request to invite a third user(e.g., expert) to collaborate, a screen touch that selects an object(e.g., gaskets) in a repair schematic that is displayed in an onlinecollaborative workarea 1037, spoken statements, typed statements, etc.Requests may be stored as request information 1010 in the context 1002corresponding to communications received via the user interface 1012from the mobile device 112.

EXAMPLE

A vehicle 104 owner is changing an oil filter using their electronictablet (e.g., iPad) to view maintenance instructions provided by onlinemarketplace XYZ Motors. The user is experiencing problems. The useropens the whiteboard app (“WHITEBOARD APPLICATION”) provided by XYZMotors on their tablet, A) adds a context 1002 describing the vehicle(e.g., 1967 Ford Mustang) and describing the repair (“OIL FILTERCHANGE”) to initiate a collaborative workspace session; and B) attachesthe context 1002 to the online collaborative workspace 1014.

<whiteboard initializes w/vehicle make/model/year and repair schematic>

<collaborative workspace session begins>

<user requests assistance via the user interface 1012>

<expert who responds via the user interface 1012>

(O)wner: “Hey—I can't figure this out—it keeps leaking even though I'vetightened it up”

(E)xpert: “Have you replaced the gaskets?”

O: “Ummm . . . What gaskets?”

E: <taps on the gaskets within the repair schematic>

<automatic display of set of gaskets (e.g., Fram) in metadata on userinterface 1012 that may be utilized to complete the repair described bythe repair schematic>

<drags one of the item images to the online collaborative workarea 1037>

<schematic automatically highlights the gasket location tapped by theexpert>

“They look like this . . . ”

O: “Huh! no—thought I could reuse the old one . . . ”

<drags the link to a shopping cart on the user interface 1012>

“I'll grab one of those tomorrow. Thanks!”

<tips the expert an ‘eBuck’ for his time>

<collaborative workspace session ends>

Later that evening, the user again launches the whiteboard app(“WHITEBOARD APPLICATION”), identifies the above mentioned context 1002in the directory and reattaches the context 1002 by executing the “addcontext” command to initiate a second session for the same context 1002.The user returns to the item in their shopping cart which is accessiblevia the user interface 1012 and selects a user interface elementinvoking an “IN-STORE PICK UP” to purchase the item from a store that islocated within a predetermined distance of the mobile device 112. Thenetwork-based marketplace 118 utilizes the context 1002 to suggest adifferent item (e.g., second item) (e.g., another brand that ispreferred by the user) based on the context 1002. For example, thecontext 1002 may be accessed to identify a second item and present thesecond item as being available through a local merchant's “IN-STOREPICK-UP” feature of XYZ motors (e.g., network-based marketplace 118), ordirectly from XYZ motors (e.g., network-based marketplace 118). The userpurchases the second item via the shopping cart that is accessed via theuser interface 1012 that is accessed via the whiteboard app.

In another embodiment, the user does not re-launch the whiteboard appbut, instead, opens their shopping cart directly and is presented withthe item and a presentation of a second item that is selected based onthe context 1002 being associated with the user who opens the shoppingcart (e.g., a brand preferred by the user who opens the shopping cart).The user completes the purchase after selecting the IN-STORE PICK-UPfeature, picks up the part along their bus ride home the next day, andreceives a ‘continue my repair’ notification on their tablet after thepurchase is completed.

Returning to the general discussion, further examples may includeutilization of the “add context” command to create other contexts 1002for different repairs of the same vehicle or for repairing othervehicles. Further examples may also include, re-launching the whiteboardapplication and reattaching a context 1002 that was previouslyinitialized and/or utilized. It will be appreciated by one skilled inthe art that a user may, at any time, open one or more instances of thewhiteboard application on multiple devices including a mobile device 112and/or a client machine 120. Further, each device may display adifferent type of information (e.g., participant information, metadatainformation 1018, etc.) in the user interface 1012 and receive differentinformation. For example, a first device (e.g., mobile) device 112 maybe utilized for camera, voice, and sensor 108 functionality, a seconddevice (e.g., laptop) may be utilized for interactive chat and shoppingcart information and a third device (e.g., tablet or Google Glass) maybe utilized to view and interact with a repair schematic or document. Itwill further be appreciated by one skilled in the art that the interfaceinformation described above may be embodied in interfaces other than theuser interface 1012. For example, the interface information may beembodied in an audio interface, a machine interface, applicationprogramming interface (API), a haptic interface or any other boundaryacross which two or more systems meet and act on each other or two ormore users communicate with each other or any combination thereof.

FIG. 10B illustrates a context panel 1030, according to an embodiment.The context panel 1030 may be utilized to display context information1028. The context information 1028 may include the context 1002including the initialization information 1008 and other informationutilized to characterize a context 1002 for a particular onlinewhiteboard collaboration. The initialization information 1008 mayinclude the year, make, model and repair for which the user desires tocollaborate. Other information may include part description information304 that is displayed responsive to the network-based marketplace 118comparing the initialization information 1008 with vehicle information300 in the garage information 706 in the user profile information 702associated with the user who attached the context 1002 and identifying amatch according to vehicle 104 (e.g., Ford Mustang 1967) and part 106(e.g., oil filter). For example, the part description information 304 inthe identified vehicle information 300 may include an indicator (“YES”)indicating a smart component 102 (e.g., oil filter) was reported in ascan of 1967 Ford Mustang. The part description information 304 that isdisplayed may further include characterization information 312 toindicate a percentage of wear (e.g., 90%) or multiple samples ofcharacterization information 312 that are processed (e.g., averaged) toindicate a percentage of wear (e.g., 90%) that is further associatedwith service level information 318 that registers a service level (e.g.,“REPLACE”), the OEM authentic information 320 (e.g., original equipmentmanufacturer (OEM)) including a flag that is asserted to signify thepart 106 is manufactured by an original equipment manufacturer, the parttype identifier 308 (“OIL FILTER”), and the part identifier 306 all aspreviously described. Further, portions of the user profile information702 for the user who attached the context 1002 may be displayedincluding an expertise level included in the expert information 220(“NOVICE”) indicating the present user is a novice with regard toinstalling oil filters and user preference information 704 indicatingthe user has expressed an interest in a particular brand of the oilfilter (e.g., “FRAM”).

Other embodiments may not utilize the context panel 1030 to display thecontext information 1028. For example, other embodiments may display allor part of the context information 1028 as discrete user interfaceelements on the user interface 1012 or as groups of user interfaceelements on the user interface 1012. Further, other embodiments of thepresent disclosure may display other types of information in the contextpanel 1030. For example, other embodiments of the present disclosure maydisplay discrete user interface elements or groups of user interfaceelements of participant information 1016, metadata information 1018,elements from the online collaborative workarea 1037, search information1020, tool information 1022, dialogue information 1024, shopping cartinformation 1026, advertising information 1033 and promotionalinformation 1035 in the context panel 1030.

FIG. 10C illustrates a shopping cart panel 1032, according to anembodiment. The shopping cart panel 1032 may be utilized to displayshopping cart information 1026. The shopping cart information 1026 mayinclude items the user intends to purchase (e.g., “FRAM EXTRAT GUARD . .. ”). For example, the shopping cart information 1026 may include itemsthe user intends to purchase that were selected from other parts of theuser interface 1012 (e.g., other panels) and dragged to the shoppingcart panel 1032. The shopping cart information 1026 may include itemsother users purchased for similar repairs for similar vehicles(“MOTORCRAFT OIL . . . ”). The shopping cart information 1026 mayfurther include in-store pick-up availability for items within apredetermined distance (e.g., five miles) of the current location of themobile device 112. For example, the “FRAM EXTRA GUARD . . . ” oil filtermay be picked up at a Napa Auto Parts store or an O'Reilly's Auto Partsstore both within five miles of the current location of the mobiledevice 112. Further illustrated are buttons (“INFO”) respectivelycorresponding to the stores that may be selected for in-store pick-up.The buttons may be selected to display store information including a mapincluding driving instructions to the store, open hours for the store,and contact information for the store including a link to a website forthe store. Other embodiments may not utilize the shopping cart panel1032 to display the shopping cart information 1026. For example, otherembodiments may display all or part of the shopping cart information1026 as discrete user interface elements on the user interface 1012 oras groups of user interface elements on the user interface 1012.Further, other embodiments may display other types of information in theshopping cart panel 1032. For example, other embodiments may displaydiscrete user interface elements or groups of user interface elements ofparticipant information 1016, metadata information 1018, elements fromthe online collaborative workarea 1037, search information 1020, toolinformation 1022, dialogue information 1024, advertising information1033 and promotional information 1035 in the shopping cart panel 1032.

FIG. 10D illustrates a metadata panel 1034, according to an embodiment.The metadata panel 1034 may be utilized to display metadata information1018. The metadata panel 1034 may be used as an additional and separateworkspace. The metadata panel 1034 may be used to display and manipulateinstances of objects that are presently being displayed on another partof the user interface 1012 such as the online collaborative workarea1037. For example, the online collaborative workarea 1037 illustrates arepair schematic including a user interface element 1036 representing anobject in the form of an archetypical set of gaskets used in thereplacement of an oil filter. Selection of the user interface element1036 by one of the users (e.g., an expert) may cause the user interfaceelement 1036 to be highlighted, an automatic initiation of a search forlistings 600 describing gaskets that are being offered for sale on thenetwork-based marketplace 118 that match the selected archetypical setof gaskets and display of three sets of gaskets in the metadata panel1034 that match the description of archetypical set of gaskets as wellas the user-preferred brands of the user in accordance with userpreference information 704 in the user profile information 702associated with the user who attached the context 1002. In anotherexample, the gasket sets may be matched in accordance with theuser-preferred brands of the user who selected user interface element1036. For example, the user who selected the user interface element 1036may be a user other than the user who attached the context 1002 and thegasket sets may be matched in accordance with the user-preferred brandsincluded in the user preference information 704 in the user profileinformation 702 of that user. Other user interface elements (e.g., textbox, links, and illustrations) representing objects on the onlinecollaborative workspace 1014 may be dragged to the metadata panel 1034.Further, a gasket set may be selected from the metadata panel 1034 anddragged to the shopping cart panel 1032 (not shown) for purchase. Otherembodiments may not utilize the metadata panel 1034 to display themetadata information 1018. For example, other embodiments may displayall or part of the metadata information 1018 as discrete user interfaceelements on the user interface 1012 or as groups of user interfaceelements on the user interface 1012. Further, other embodiments maydisplay other types of information in the metadata panel 1034. Forexample, other embodiments may display discrete user interface elementsor groups of user interface elements of participant information 1016,elements from the online collaborative workarea 1037, search information1020, tool information 1022, dialogue information 1024, advertisinginformation 1033 and promotional information 1035 in the metadata panel1034.

FIG. 10E illustrates a search panel 1038, according to an embodiment.The search panel 1038 may be utilized to display search information1020. The search panel 1038 may be used to automatically or manuallysearch for listings 600 on the network-based marketplace 118. To thisend, the search panel 1038 may include an input box 1040 to receive aquery to initiate a manual search and a search result box 1042 todisplay the search result including descriptions of listings 600 ofitems being offered for sale on the network-based marketplace 118 andlinks to the listings 600. An automatic search may be initiated byselecting an object from the user interface 1012 (not shown)corresponding to an item that may be offered for sale on thenetwork-based marketplace 118. For example, the online collaborativeworkarea 1037 illustrates a repair schematic including a user interfaceelement 1036 representing an object in the form of an archetypical setof gaskets used in the replacement of an oil filter. Selection of theuser interface element 1036 by one of the users (e.g., expert) may causethe user interface element 1036 to be highlighted and an automaticinitiation of a search for listings 600 describing gaskets that arebeing offered for sale on the network-based marketplace 118. The searchresult box 1042 may include a search result including listings 600 thatmatch the selected archetypical set of gaskets. The search result may besorted and displayed in the search result box 1042. The search resultmay be sorted based on the brand preferences of the user that initiatedthe search. In another embodiment, the search result may be sorted basedon the preferences of the user that attached the context 1002. In bothinstances the user-preferred brands of the user may be found in the userpreference information 704 in the user profile information 702 for theuser. Selections of other objects from other panels may alsoautomatically initiate a search. Further, a listing 600 (not shown) inthe search result box 1042 may be selected and dragged to the shoppingcart panel 1032 (not shown) for purchase or to another panel. Otherembodiments may not utilize the search panel 1038 to display the searchinformation 1020. For example, other embodiments may display all or partof the search information 1020 as discrete user interface elements onthe user interface 1012 or as groups of user interface elements on theuser interface 1012. Further, other embodiments may display other typesof information in the search panel 1038. For example, other embodimentsmay display discrete user interface elements or groups of user interfaceelements of participant information 1016, elements from the onlinecollaborative workarea 1037, tool information 1022, dialogue information1024, search information 1020, advertising information 1033 andpromotional information 1035 in the search panel 1038.

FIG. 10F illustrates a tool panel 1043, according to an embodiment. Thetool panel 1043 may be utilized to display tool information 1022. Thetool information 1022 may include tools to control the user interface1012. For example, the tools may be utilized to open and close panels onthe user interface 1012. Further, the tool information 1022 may includetools to control the contents of the user interface 1012. For exampletool information 1022 may include tools to create, delete, modify, ormanipulate text, illustrations, objects, or user interface elements onthe user interface 1012. Other embodiments may not utilize the toolpanel 1043 to display the tool information 1022. For example, otherembodiments may display all or part of the tool information 1022 asdiscrete user interface elements on the user interface 1012 or as groupsof user interface elements on the user interface 1012. Further, otherembodiments may display other types of information in the tool panel1043. For example, other embodiments may display discrete user interfaceelements or groups of user interface elements of participant information1016, elements from the online collaborative workarea 1037, dialogueinformation 1024, and search information 1020 in the tool panel 1043.

FIG. 10G illustrates a dialogue panel 1044, according to an embodiment.The dialogue panel 1044 may be utilized to display dialogue information1024. The dialogue information 1024 may include scripts representingspoken words, typed words, messaged words, etc. and generally anystatement (e.g., declarative, question, etc.) submitted by any userwhether in the present or previous online collaborative session. Thedialogue information 1024 may be analyzed based on the context 1002 toidentify words as relevant. Merely for example, the network-basedmarketplace may parse the dialogue information 1024 based on the context1002 to generate a parse result including words that register at a highfrequency of occurrence in the dialogue information 1024 and filteredusing a dictionary of parts 102 (e.g., Chilton's Automotive RepairManual for repair of automobiles) to identify a parsed result includingwords in the dialogue information 1024 for highlighting and hyperlinkingto automatically initiate searches on the network-based marketplace 118.For example, the highlighted word or phrase may be selected to initiatea search query for listings 600 on the network-based marketplace 118 byutilizing the highlighted word or phrase as a query for the search.Other embodiments may not utilize the dialogue panel 1044 to display thedialogue information 1024. For example, other embodiments may displayall or part of the dialogue information 1024 as discrete user interfaceelements on the user interface 1012 or as groups of user interfaceelements on the user interface 1012. Further, other embodiments maydisplay other types of information in the dialogue panel 1044. Forexample, other embodiments may display discrete user interface elementsor groups of user interface elements of participant information 1016,elements from the online collaborative workarea 1037, tool information1022, search information 1020, advertising information 1033 andpromotional information 1035 in the dialogue panel 1044.

FIG. 10H illustrates a participant panel 1046, according to anembodiment. The participant panel 1046 may include one or more userpanels 1048 to display participant information 1016. Each user panel1048 may present a user on the network-based marketplace 118 (notshown). The user panel 1048 may present the user who attached thecontext 1002 (e.g., “JOHN DOE”) and one or more other users (e.g.,experts, “EXPERT 1: JANE DOE”) who participate in a session. The expertsmay be selected for presentation based on expert information 220 (notshown) in the user profile information 702 (not shown) associated withthe user, as described later. The presentation of the user in the userpanel 1048 may include an image of the user (e.g., expert), a user name,a user affiliated electronic storefront, a merchandising element 1050,and a tip box 1052. Selection of the user name or image may communicatea notice to the user (e.g., expert) including an inquiry asking the userto join a session. The merchandising element 1050 may be updated by theassociated user to present a featured promotion, discount, or coupon(s)that may be selected to participate in the featured promotion (e.g.,print the coupon, buy an item to obtain a discount, etc.). The tip box1052 may receive a tip for the associated user. For example, the tip box1052 may receive five USD that is credited to the associated user'sPayPal account (e.g., “EXPERT 2: JIM DOE”) and debited from the tippinguser's PayPal account (e.g., “OWNER: JOHN DOE”). Other embodiments maynot utilize the participant panel 1046 to display the participantinformation 1016. For example, other embodiments may display all or partof the participant information 1016 as discrete user interface elementson the user interface 1012 or as groups of user interface elements onthe user interface 1012. Further, other embodiments may display othertypes of information in the participant panel 1046. For example, otherembodiments may display discrete user interface elements or groups ofuser interface elements of search information 1020, elements from theonline collaborative workarea 1037, tool information 1022, searchinformation 1020, advertising information 1033 and promotionalinformation 1035 in the participant panel 1046.

FIG. 10I illustrates the network-based marketplace 118, according to anembodiment. The network-based marketplace 118 may include smartcomponent modules 500 and a database 204. The network-based marketplace118, smart component modules 500 and database 204 operate as previouslydescribed and further as follows. The smart component modules 500 mayinclude a receiving module 502 and a processing module 504. Thereceiving module 502 may receive commands, requests and otherinformation from the mobile device 112 (not shown) or a client machine120 (not shown). For example, the commands may include the “add context”command, the “attach context” command or other commands, as previouslydescribed. Further for example, the receiving module 502 may receiverequests describing interactions received via the user interface 1012(not shown). The processing module 504 may process the commands,requests and other information to update the database 204 and respond tothe aforementioned commands, requests and other information bycommunicating the user interface 1012, updates to the user interface1012, or portions of the user interface 1012 to the mobile device(s) 112or the client machine(s) 120 in accordance with the one or moreparticipants of a session. The database 204 may include the items table506, the user table 508 and other data structures previously describedthough not presently shown. The user table 508 may include user profileinformation 702. Each entry of user profile information 702 may storeone or more contexts 1002 (not shown) for a particular user.

FIG. 10J illustrates user profile information 702, according to anembodiment. The user profile information 702 operates as previouslydescribed and as described below. The user profile information 702 mayinclude user information 216 and user preference information 704including expert information 220. Recall the expert information 220 mayinclude one or more part type identifiers 308, one or more sub-systemidentifiers 708 and vehicle identification information 302 that mayidentify one or more vehicles 104 for which the user is ranked. The userranking may be utilized to identify content for consumption by a user orto identify a source of content for consumption by a user. For example,the expert information 220 may indicate that a user has the ability tosource content for another user by providing “expert” or “qualified”advice (e.g., verbal content) for a particular part 106 (not shown), ina particular sub-system 103 (not shown), in a particular vehicle 104(not shown), or some combination thereof. The processing module 504 (notshown) may identify a user who is qualified as an expert to work on therepair and vehicle 104 (not shown) specified in the context 1002 bycomparing the initialization information 1008 in the context 1002 withthe expert information 220 to identify a match. For example, portions ofthe expert information 220 may be compared with the initializationinformation 1008 in the context 1002 (not shown) to identify a match. Afuzzy match may constitute a match. For example, overlapping part typeidentifiers 308 and/or overlapping vehicle identification information302 may constitute a match. The processing module 504 (not shown) mayfurther utilize the expert information 220 to select content forconsumption by a user who attaches the context 1002 to the onlinecollaborative workspace 1014. Merely for example, the expert information220 may include an expertise level that ranks the ability of the user toconsume content with four levels of qualification information including“NOVICE,” “INTERMEDIATE,” “SENIOR,” and “EXPERT” that may be utilized toselect content for the user for the indicated field of expertise (e.g.,part type, sub-system, vehicle). For example, the processing module 504may select repair schematics with brief and terse instructions for auser at the “EXPERT” level and repair schematics that are exhaustive fora user at the “NOVICE” level. Continuing with the example, theschematics that are exhaustive may include additional and/or moredetailed illustrations and additional or more detailed description.Further, the processing module 504 may upgrade or downgrade theexpertise level in the expert information 220 for the user based on theamount of assistance provided to perform a repair or the quality ofassistance provided to perform a repair.

The user profile information 702 further includes context directoryinformation 1054 and an online collaborative workplace marker 1056. Thecontent directory information 1054 may store the context 1002 for theuser. For example, the contexts 1002 created by the user with the “addcontext” command are stored in the user profile information 702 untilremoved with a “delete context” command. The online collaborativeworkplace marker 1056 may be used to store a context identifier 1004 fora particular context 1002. Responsive to execution of the “attachcontext” command, the context identifier 1004 that is being received bythe “attach context” command is stored in the online collaborativeworkplace marker 1056 constituting attachment of the context 1002 to theonline collaborative workspace 1014. Subsequent executions of the“attach context” command overwrite the context identifier 1004 stored bythe previous execution of the “attach context” command. That is, only asingle context identifier 1004 is utilized by the network-basedmarketplace 118 for the whiteboard application.

FIG. 10K illustrates context directory information 1054, according to anembodiment. The context directory information 1054 may include one ormore entries of context 1002. An entry of context 1002 may be added tothe context directory information 1054 with the “add context” commandand removed from the content directory information 1054 with the “deletecontext” command

FIG. 10L illustrates the context 1002, according to an embodiment. Thecontext 1002 may include the context identifier 1004, the initializationinformation 1008, and the request information 1010, as previouslydescribed.

FIG. 10M illustrates the request information 1010, according to anembodiment. The request information 1010 may include one or moresessions 1058, as previously described. A session 1058 may be initiatedwith execution of an “attach context” command. A session 1058 may beterminated by closing the whiteboard app. Reattachment initiates a newsession 1058 for a particular context 1002.

FIG. 10N illustrates a session 1058, according to an embodiment. Thesession 1058 may include one or more requests 1060, as previouslydescribed. The request 1060 may be stored in the session 1058 responsiveto the request 1060 being received at the network-based marketplace 118.

FIG. 10O illustrates the request 1060, according to an embodiment. Therequest 1060 may include a request identifier 1062, a timestamp 314,operation information 1064, and response information 1066. The requestidentifier 1062 may be sequentially allocated and assigned to therequest 1060 responsive to receiving the request 1060. The requestidentifier 1062 may uniquely identify the request 1060 for theparticular session 1058. The timestamp 314 is stored in the request 1060responsive to receipt of the request 1060 via the user interface 1012(not shown) at the mobile device 112 (not shown) or client machine 120(not shown). The operation information 1064 may include an operation(e.g., operation code) describing the type of operation requested andone or more parameters. For example, operations may include attaching acontext 1002, adding an expert to the session 1058, selecting an object(e.g., user interface element for a part 106), moving a part 106 fromthe metadata panel 1034 (not shown) to the shopping cart panel 1032 (notshown), scroll dialogue information 1024, etc. Further each operationmay be associated with one or more parameters that are received as inputfor the operation. For example, one or more parameters may be receivedvia the user interface 1012 from the mobile device 112 or the clientmachine 120. The response information 1066 may store informationutilized to respond to the request 1060 including interface information.For example, the request 1060 may indicate the user selected a userinterface element representing an item that triggered a search and theresponse information 1066 may include interface information includingsearch information 1020 including the search results that wereidentified based on the search executed.

FIG. 10P illustrates response information 1066, according to anembodiment. The response information 1066 may include informationutilized to respond to the operation in the request 1060. For examplethe response information may include interface information includingparticipant information 1016, metadata information 1018, searchinformation 1020, tool information 1022, dialogue information 1024,shopping cart information 1026, and information generated for display inthe online collaborative workarea 1037 or any other part of the userinterface 1012. Further, the response information may includeinformation that is generated based on the request 1060 but not accessedvia the user interface 1012 (e.g., search results generated in responseto a request 1060 but not displayed on the user interface 1012). Merelyfor example, the response information 1066 may include one or more useridentifiers 218, expert identifier information 930, one or more savedsearches 1067 including query and search results, one or more listingidentifiers 308, one or more part identifiers 306, one or more part typeidentifiers 308, and the context identifier 1004, as previouslydescribed. The user identifiers 218 may include and distinguish the useridentifier 218 associated with the mobile device 112 that is currentlyexecuting the whiteboard application and other use identifiers (e.g.,expert 1, expert 2, etc.). The mobile device identifier 1069 mayidentify the mobile device 112 from which the request 1060 originated.The client machine identifier 1071 may identify the client machine 120from which the request 1060 originated.

FIG. 10Q illustrates feature element information 1070, according to anembodiment. The feature element information 1070 may include one or morefeature elements 1072. Each feature element 1072 corresponds to afeature that is supported by the online collaborative workspace 1014.The processing module 505 may utilize the feature element information1070 to process corresponding feature information 1006. For example, aparticipant feature corresponds to the participant information 1016, ametadata feature corresponds to the metadata information 1018, an onlinecollaborative workarea feature corresponds to information processed inthe online collaborative workarea 1037, a search feature corresponds tothe search information 1020, a tool feature corresponds to toolinformation 1022, a dialogue feature corresponds to dialogue information1024, a shopping cart feature corresponds to shopping cart information1026, a context feature corresponds to context information 1028, anadvertising feature corresponds to advertising information 1033 and apromotional feature corresponds to promotional information 1035. Otherembodiments may include additional or fewer features.

FIG. 10R illustrates a method 1074, according to an embodiment, to add acontext 1002. The method 1074 may commence at operation 1076, at thenetwork-based marketplace 118, with the receiving module 502 receivingthe initialization information 1008. The message may be received from amobile device 112 or a client machine 120. The message may include useridentifier 218, an indication to add the context 1002, and theinitialization information 1008. For example, the user may haveinteracted with a set of screens that were displayed at the mobiledevice 112 that, in turn, communicated the message over the network 116to the network-based marketplace 118. At operation 1078, the processingmodule 504 may allocate the context 1002, allocated by the contextidentifier 1004, store the initialization information 1008 in thecontext 1102, and store the context identifier 1004 in the context 1002.Further, the processing module 504 may store the context 1002 in thecontext directory information 1054 in the user profile information 702that is identified based on the user identifier 218. At operation 1080,the processing module 504 may communicate the context identifier 1004over the network 116 to the mobile device 112 or the client machine 120that executed the “add context” command.

FIG. 10S illustrates a method 1082, according to an embodiment, toattach a context 1002. The method 1082 may commence at operation 1084,at the network-based marketplace 118, with the receiving module 502receiving a request 1060 to attach a context 1002. The request mayinclude the context identifier 1004. For example, the receiving module502 may receive the request 1060 from over a network 116 from the mobiledevice 112 or the client machine 120. The request 1060 may include theuser identifier 218 to identify the user making the request 1060, and anoperation 1068 to attach the context 1002, and the context identifier1004. For example, the user may have selected a user interface elementrepresenting the context 1002 from a screen displayed at the mobiledevice 112 that, in turn, communicated the request 1060 over the network116 to the network-based marketplace 118. At operation 1086, theprocessing module 504 may attach the context 1002 to the onlinecollaborative workspace 1014 in the whiteboard application. For example,the processing module 504 may store the context identifier 1004 in theonline collaborative workspace marker 1056 in the user profileinformation 702 that is identified based on the user identifier 218 inthe request 1060. Other embodiments may utilize the mobile deviceidentifier 1069 and/or the client machine identifier 1071 in the request1060 to identify the appropriate user profile information 702 with amapping operation. The processing module 504 overwrites the contextidentifier 1004 previously stored in the online collaborative workspacemarker 1056 with the context identifier 1004 received in the request1060 and creates a new session in the request information 1010. Further,the processing module 504 may indicate an end of session 1058 for thecontext identifier 1004 previously stored in the online collaborativeworkspace marker 1056. At operation 1088, the processing module 504 mayprocesses the request 1060 based on the context 1002. For example, theprocessing module 504 may utilize the context identifier 1004 and therequest 1060 to update the user interface 1012 at the mobile device 112or generate a new user interface 1012 at the mobile device 112. Theoperation 1088 is described further as the method 1003 in FIG. 10U. Atoperation 1090, the processing module 504 stores the request 1060 in thesession 1058 in the request information 1010 in the context 1002.

FIG. 10T illustrates a method 1092, according to an embodiment, toreceive and process a request. The method 1092 may commence at operation1094, at the network-based marketplace 118, with the receiving module502 receiving a request 1060. For example, a mobile device 112 mayinitially receive the request 1060 responsive to sensing a touch on auser interface 1012 and communicate the request 1060 over the network116 to the network-based marketplace 118 that, in turn, includes thereceiving module 502 that, in turn, receives the request.

At operation 1096, the processing module 504 may identify the context1002 based on the request 1060. For example, the processing module 504may utilize the user identifier 218 in the operation information 1064 inthe request 1060 to identify the corresponding user profile information702 including the appropriate online collaborative workspace marker1056. It will be appreciated that the processing module 504 may map arequest 1060 that is received from an expert to the user who initiatedthe session 1058 and the session 1058 to properly identify theappropriate online collaborative workspace marker 1056. Otherembodiments may utilize the mobile device identifier 1069 or the clientmachine identifier 1071 in the request 1060 to identify the appropriateuser profile information 702 with a mapping operation that identifiesthe user based on the device identifier 1069 or the client machineidentifier 1071. Further, at operation 1096, the processing module 504may read the context identifier 1004 from the collaborative workspacemarker 1056.

At operation 1098, the processing module 504 may process the request1060 based on the context 1002. For example, the processing module 504may utilize the context identifier 1004 and the request 1060 to updatethe user interface 1012 or generate a new user interface 1012 andcommunicate the update or new user interface 1012 to the mobile device112. The operation 1098 is described further as the method 1003 in FIG.10U. At operation 1001, the processing module 504 may store the request1060 in the most recent session 1058 in the request information 1010 inthe context 1002.

FIG. 10U illustrates a method 1003, according to an embodiment, toprocess a request 1060 based on a context 1002. The method 1003 may beentered from operation 1088 of FIG. 10S or from operation 1098 of FIG.10T. Recall that a request 1060 (e.g., received request) was receivedover the network 116, the received request 1060 originating from thewhiteboard app at a mobile device 112 (though the app may also beexecuted on the client machine 120). Broadly, the method 1003 maygenerate response information 1066 for the received request 1060 basedon context 1002 including the initialization information 1008 and therequest information 1010. The method 1003 may generate interfaceinformation in at least two ways. First, the method 1003 may generateinterface information based on the response information 1066respectively stored in all of the previous requests 1060, theinitialization information 1008, and the received request 1060 for everyfeature (e.g., participating feature, shopping cart feature, etc.)presently supported by the whiteboard app. Further, the method 1003 maygenerate interface information based on the initialization information1008 and the received request 1060 for every feature (e.g.,participating feature, shopping cart feature, etc.) presently supportedby the whiteboard app. Accordingly, the entire context 1002 is reviewedover time (e.g., all previous requests 1060) for every feature (e.g.,participating feature, shopping cart feature, etc.) to generate theinterface information that, in turn, may be utilized to generate theuser interface 1012 that, in turn, is communicated over the network 116to the mobile device 112 or client machine 120.

At operation 1005, the processing module 504 may advance to the firstfeature element 1072 (e.g., current feature) in the feature elementinformation 1070 (e.g., participant feature, metadata feature, etc.). Atoperation 1007, the processing module 504 may advance to the firstsession 1058 (e.g., current session) in the request information 1010 inthe context 1002 in the user profile information 702 identified based onthe received request 1060. At operation 1009, the processing module 504may advance to the first request 1060 (e.g., current request) in thecurrent session 1058.

At operation 1011, the processing module 504 may generate interfaceinformation based on the response information 1066 in the currentrequest 1060, the received request 1060 and the current feature (e.g.,participant feature). For example, the processing module 504 maygenerate interface information including a list of user identifiers 218that identify expert users responsive to identifying the current request1060 as including operation information including an operation (e.g., opcode) that describes a request for expert assistance and identifying theresponse information 1066 for the current request 1060 as including alist of user identifiers 218 that identify expert users (e.g.,previously consulted experts). Further for example, the processingmodule 504 may generate the interface information to open, close, oraugment a panel (e.g., dialogue panel 1044) corresponding to the currentfeature (e.g., dialogue feature). Further for example, the processingmodule 504 may generate interface information to add (e.g., expert),remove, or augment user interface elements for corresponding to thecurrent feature (e.g., participant feature).

At decision operation 1013, the processing module 504 may identifywhether more requests 1060 are in the current session 1058. If morerequests 1060 are in the current session 1058 then processing continuesat operation 1015. Otherwise, processing continues at decision operation1017. At operation 1015, the processing module 504 advances to the nextrequest 1060 and continues processing at operation 1011.

At decision operation 1017, the processing module 504 may identifywhether more sessions 1058 are in the request information 1010associated with the received request 1060. If more sessions 1058 are inthe request information 1010 then processing continues at operation1019. Otherwise, processing continues at decision operation 1023. Atoperation 1019, the processing module 504 may advance to the nextsession 1058 and continue processing at operation 1009.

At decision operation 1023, the processing module 504 may identifywhether more features elements 1072 are present in the feature elementinformation 1070. If more features elements 1072 are present in thefeature element information 1070 then processing continues at operation1025. Otherwise, processing continues at operation 1027. At operation1025, the processing module 504 may advance to the next feature element1072 and continue processing at operation 1007.

At operation 1027, the processing module 504 may generate interfaceinformation based on the initialization information 1008 in the context1002, the received request 1060 and all features (e.g., participantfeature). For example, the processing module 504 may generate interfaceinformation to open, close, or augment any of the aforementioned panelsincluding a context panel, the shopping cart panel 1032, the metadatapanel 1034, the search panel 1038, the dialogue panel 1044 and theparticipant panel 1046. Further for example, the processing module 504may generate interface information to add, remove, or augment userinterface elements for participant information 1016, metadatainformation 1018, the online collaborative workarea 1037, the searchinformation 1020 the tool information 1022, the dialogue information1024, the shopping cart information 1026 the context information 1028,advertising information 1033 and promotional information 1035. Furtherfor example, the processing module 504 may utilize service levelinformation 318 and other information in the part descriptioninformation 304 of vehicle information 300 in the garage information 706of the user for smart components 102 that match or fuzzy match theinitialization information 1008 in the context 1002 and update thecontext panel 1030 display “SMART COMPONENT WEAR: 90%” based on theidentified match.

At operation 1029, the processing module 504 may generate the userinterface 1012 based on the interface information that was generated inoperations 1011 and 1027 and communicate the user interface 1012 overthe network 116 to the mobile device 112 or the client machine 120 thatoriginated the request 1060. In another example, the processing module504 may communicate the interface information over the network 116 toupdate the user interface 1012 or a portion of the user interface 1012that is being displayed on mobile device 112 or the client machine 120.

At operation 1031, the processing module 504 may store the interfaceinformation that was generated in operations 1011 and 1027 in theresponse information 1066 for the received request 1060.

FIG. 11 illustrates network architecture 1100, according to anembodiment. A networked system 1102, in an example form of anetwork-server-side functionality, is coupled via a communicationnetwork 1104 (e.g., the Internet, wireless network, cellular network, ora Wide Area Network (WAN)) to one or more client devices 1110 and 1112.The networked system 1102 corresponds to the system 100 in FIG. 1, thenetwork-based marketplace 118 in FIG. 5, the system 800 in FIG. 8A, thesystem 900 in FIG. 9A, and the system 1000 in FIG. 10A, accordingly, thesame or similar references have been used to indicate the same orsimilar features unless otherwise indicated. FIG. 11 illustrates, forexample, a web client 1106 operating via a browser (e.g., such as theINTERNET EXPLORER® browser developed by Microsoft® Corporation ofRedmond, Wash. State), and a programmatic client 1108 executing onrespective client devices 1110 and 1112.

The network architecture 1100 may be utilized to execute any of themethods described in this document. The client devices 1110 and 1112 maycomprise a mobile phone, desktop computer, laptop, or any othercommunication device that a user may utilize to access the networkedsystem 1102. In some embodiments, the client device 1110 may comprise adisplay module (not shown) to display information (e.g., in the form ofuser interfaces). In further embodiments, the client device 1110 maycomprise one or more of a touch screen, accelerometer, camera,microphone, and GPS device. The client devices 1110 and 1112 may be adevice of a user that is used to perform a transaction involving digitalgoods within the networked system 1102. In one embodiment, the networkedsystem 1102 is a network-based marketplace that manages digital goods,publishes publications comprising item listings of products available onthe network-based marketplace, and manages payments for thesemarketplace transactions. Additionally, external sites 1128, 1128′ maybe sites coupled to networked system 1102 via network 1104. Externalsites may be any desired system, including ecommerce systems.

An Application Program Interface (API) server 1114 and a web server 1116are coupled to, and provide programmatic and web interfaces respectivelyto, one or more application servers 1118. The application server(s) 1118host a publication system 1200 and a payment system 1122, each of whichmay comprise one or more modules, applications, or engines, and each ofwhich may be embodied as hardware, software, firmware, or anycombination thereof. The application servers 1118 are, in turn, coupledto one or more database servers 1124 facilitating access to one or moreinformation storage repositories or database(s) 1126. In one embodiment,the databases 1126 are storage devices that store information to beposted (e.g., publications or listings) to the publication system 1200.The databases 1126 may also store digital goods information inaccordance with example embodiments.

In example embodiments, the publication system 1200 publishes content ona network (e.g., Internet). As such, the publication system 1200provides a number of publication and marketplace functions and servicesto users that access the networked system 1102. The publication system1200 is discussed in more detail in connection with FIG. 12. In exampleembodiments, the publication system 1200 is discussed in terms of anonline marketplace environment. However, it is noted that thepublication system 1200 may be associated with a non-marketplaceenvironment such as an informational (e.g., search engine) or socialnetworking environment.

The payment system 1122 provides a number of payment services andfunctions to users. The payment system 1122 allows users to accumulatevalue (e.g., in a commercial currency, such as the U.S. dollar, or aproprietary currency, such as points, miles, or other forms of currencyprovide by a private entity) in their accounts, and then later to redeemthe accumulated value for products (e.g., goods or services) that aremade available via the publication system 1200 or elsewhere on thenetwork 1104. The payment system 1122 also facilitates payments from apayment mechanism (e.g., a bank account, PayPal™, or credit card) forpurchases of items via any type and form of a network-based marketplace.

While the publication system 1200 and the payment system 1122 are shownin FIG. 11 to both form part of the networked system 1102, it will beappreciated that, in alternative embodiments, the payment system 1122may form part of a payment service that is separate and distinct fromthe networked system 1102. Additionally, while the example networkarchitecture 1100 of FIG. 11 employs a client-server architecture, askilled artisan will recognize that the present disclosure is notlimited to such an architecture. The example network architecture 1100can equally well find application in, for example, a distributed orpeer-to-peer architecture system. The publication system 1200 andpayment system 1122 may also be implemented as standalone systems orstandalone software programs operating under separate hardwareplatforms, which do not necessarily have networking capabilities.

Referring now to FIG. 12, an example block diagram illustrating multiplecomponents that, in one embodiment, are provided within the publicationsystem 1200 of the networked system 1102 is shown. In this embodiment,the publication system 1200 is a marketplace system where items (e.g.,goods or services) may be offered for sale and that further implementsthe features described herein for interactive query generation andrefinement. The items may comprise digital goods (e.g., currency,license rights). The publication system 1200 may be hosted on dedicatedor shared server machines (not shown) that are communicatively coupledto enable communications between the server machines. The multiplecomponents themselves are communicatively coupled (e.g., via appropriateinterfaces), either directly or indirectly, to each other and to variousdata sources, to allow information to be passed between the componentsor to allow the components to share and access common data. Furthermore,the components may access the one or more databases 1126 via the one ormore database servers 1124, as shown in FIG. 11.

Returning to FIG. 12, the publication system 1200 provides a number ofpublishing, listing, and price-setting mechanisms whereby a buyer maylist (or publish information concerning) goods or services for sale, abuyer can express interest in or indicate a desire to purchase suchgoods or services, and a price can be set for a transaction pertainingto the goods or services. To this end, the publication system 1200 maycomprise at least one publication engine 1202 and one or more auctionengines 1204 that support auction-format listing and price settingmechanisms (e.g., English, Dutch, Chinese, Double, Reverse auctions,etc.).

A pricing engine 1206 supports various price listing formats. One suchformat is a fixed-price listing format (e.g., the traditional classifiedadvertisement-type listing or a catalog listing). Another formatcomprises a buyout-type listing. Buyout-type listings (e.g., theBuy-It-Now (BIN) technology developed by eBay Inc., of San Jose, Calif.)may be offered in conjunction with auction-format listings and allow abuyer to purchase goods or services, which are also being offered forsale via an auction, for a fixed price that is typically higher than astarting price of an auction for an item.

A store engine 1208 allows a buyer to group listings within a “virtual”store, which may be branded and otherwise personalized by and for thebuyer. Such a virtual store may also offer promotions, incentives, andfeatures that are specific and personalized to the buyer. In oneexample, the buyer may offer a plurality of items as Buy-It-Now items inthe virtual store, offer a plurality of items for auction, or acombination of both.

A reputation engine 1210 allows users that transact, utilizing thenetworked system 1102, to establish, build, and maintain reputations.These reputations may be made available and published to potentialtrading partners. Because the publication system 1200 supportsperson-to-person trading between unknown entities, in accordance withone embodiment, users may otherwise have no history or other referenceinformation whereby the trustworthiness and credibility of potentialtrading partners may be assessed. The reputation engine 1210 allows auser, for example through feedback provided by one or more othertransaction partners, to establish a reputation within the network-basedmarketplace over time. Other potential trading partners may thenreference the reputation for purposes of assessing credibility andtrustworthiness.

Navigation of the network-based marketplace may be facilitated by anavigation engine 1212. For example, a browse module (not shown) of thenavigation engine 1212 allows users to browse various category, catalog,or inventory data structures according to which listings may beclassified within the publication system 1200. Various other navigationapplications within the navigation engine 1212 may be provided tosupplement the browsing applications.

In order to make listings available via the networked system 1102 asvisually informing and attractive as possible, the publication system1200 may include an imaging engine 1214 that enables users to uploadimages for inclusion within publications and to incorporate imageswithin viewed listings. The imaging engine 1214 may also receive imagedata from a user as a search query and utilize the image data toidentify an item depicted or described by the image data.

A listing creation engine 1216 allows users (e.g., buyers) toconveniently author listings of items. In one embodiment, the listingspertain to goods or services that a user (e.g., a buyer) wishes totransact via the publication system 1200. In other embodiments, a usermay create a listing that is an advertisement or other form ofpublication.

A listing management engine 1218 allows the users to manage suchlistings. Specifically, where a particular user has authored orpublished a large number of listings, the management of such listingsmay present a challenge. The listing management engine 1218 provides anumber of features (e.g., auto-relisting, inventory level monitors,etc.) to assist the user in managing such listings.

A post-listing management engine 1220 also assists users with a numberof activities that typically occur post-listing. For example, uponcompletion of a transaction facilitated by the one or more auctionengines 1204, a buyer may wish to leave feedback regarding a particularseller. To this end, the post-listing management engine 1220 provides aninterface to the reputation engine 1210 allowing the buyer toconveniently provide feedback regarding multiple sellers to thereputation engine 1210. Another post-listing action may be shipping ofsold items whereby the post-listing management engine 1220 may assist inprinting shipping labels, estimating shipping costs, and suggestingshipping carriers.

A search engine 1222 performs searches for publications in the networkedsystem 1102 that match a query. In example embodiments, the searchengine 1222 comprises a search module (not shown) that enables keywordsearches of publications published via the publication system 1200.Further, for example, the search engine 1222 may perform the functionspreviously described in reference to the search engine 121. In a furtherembodiment, the search engine 1222 may take an image received by theimaging engine 1214 as an input for conducting a search. The searchengine 1222 takes the query input and determines a plurality of matchesfrom the networked system 1102 (e.g., publications stored in thedatabase 1126). It is noted that the functions of the search engine 1222may be combined with the navigation engine 1212. The search engine 1222,in the publication system 1200, may perform the functionality previouslydescribed with respect to the search engine 121.

A user activity detection engine 1224 in FIG. 12 may monitor useractivity during user sessions and detect a change in the level of useractivity that, as discussed in more detail below, may predict that auser is about to make a purchase. The exact amount of change in thelevel of user activity may vary. A general guideline may be to monitoracross multiple sessions and detect any significant increase over time(for example the activity level doubling or tripling in a short span).In one embodiment, when the user activity detection engine 1224 detectssuch a condition, the ecommerce system may make an intervention toprovide content for display to the user in an effort to improve theprobability that the user will make a purchase, and/or also to motivethe user to make the purchase on the ecommerce system site instead ofmoving to a competitor site in search of a better purchase. Statedanother way, activity over time and at different times before a purchaseaction provides an opportunity to personalize marketing to a user, basedon time, by intervention as discussed above. Additional examples ofincluding a temporal frame in that marketing personalization arediscussed below. The publication system 1200 may further include thesmart component modules 500, as previously described.

Although the various components of the publication system 1200 have beendefined in terms of a variety of individual modules and engines, askilled artisan will recognize that many of the items can be combined ororganized in other ways and that not all modules or engines need to bepresent or implemented in accordance with example embodiments.Furthermore, not all components of the publication system 1200 have beenincluded in FIG. 12. In general, components, protocols, structures, andtechniques not directly related to functions of exemplary embodiments(e.g., dispute resolution engine, loyalty promotion engine,personalization engines) have not been shown or discussed in detail. Thedescription given herein simply provides a variety of exemplaryembodiments to aid the reader in an understanding of the systems andmethods used herein.

Data Structures

FIG. 13 is a high-level entity-relationship diagram, illustratingvarious tables 1250 that may be maintained within the databases 1126 ofFIG. 11, and that are utilized by and support the publication system1200 and payment system 1122, both of FIG. 11. A user table 1252 maycontain a record for each of the registered users of the networkedsystem 1102. A user may operate as a seller, a buyer, or both, withinthe network-based marketplace. In one example embodiment, a buyer may bea user that has accumulated value (e.g., commercial or proprietarycurrency), and is accordingly able to exchange the accumulated value foritems that are offered for sale by the network-based marketplace.

The tables 1250 may also include an items table 1254 (e.g., items table506) in which item records (e.g., listings) are maintained for goods andservices (e.g., items) that are available to be, or have been,transacted via the network-based marketplace. Item records (e.g.,listings) within the items table 1254 may furthermore be linked to oneor more user records within the user table 1252, so as to associate aseller and one or more actual or potential buyers with an item record(e.g., listing).

A transaction table 1256 may contain a record for each transaction(e.g., a purchase or sale transaction or auction) pertaining to itemsfor which records exist within the items table 1254.

An order table 1258 may be populated with order records, with each orderrecord being associated with an order. Each order, in turn, may beassociated with one or more transactions for which records exist withinthe transaction table 1256.

Bid records within a bids table 1260 may relate to a bid received at thenetwork-based marketplace 118 in connection with an auction-formatlisting supported by the auction engine(s) 1204 of FIG. 12. A feedbacktable 1262 may be utilized by one or more reputation engines 1210 ofFIG. 12, in one example embodiment, to construct and maintain reputationinformation concerning users in the form of a feedback score. A historytable 1264 may maintain a history of transactions to which a user hasbeen a party. One or more attributes tables 1266 may record attributeinformation that pertains to items for which records exist within theitems table 1254. Considering only a single example of such anattribute, the attributes tables 1266 may indicate a currency attributeassociated with a particular item, with the currency attributeidentifying the currency of a price for the relevant item as specifiedby a seller. Another example of an attribute may include ‘fitment’(compatibility) information, which facilitates an identification ofcompatibility of a part 106 relative to other parts 106 described inother listings, smart component information and characterization, andgarage vehicle metadata.

A search table 1268 may store search information that has been enteredby a user (e.g., a buyer) who is looking for a specific type of listing.The tables 1250 may include the OEM tracking information 510, themaintenance information 512, and the smart component processinginformation 514, as previously described.

Machine

FIG. 15 is a block diagram illustrating components of a machine 1300,according to some example embodiments, able to read instructions 1324from a machine-readable medium 1322 (e.g., a non-transitorymachine-readable medium, a machine-readable storage medium, acomputer-readable storage medium, or any suitable combination thereof)and perform any one or more of the methodologies discussed herein, inwhole or in part. Specifically, FIG. 15 shows the machine 1300 in theexample form of a computer system (e.g., a computer) within which theinstructions 1324 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 1300 toperform any one or more of the methodologies discussed herein may beexecuted, in whole or in part. In alternative embodiments, the machine1300 operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine1300 may operate in the capacity of a server machine or a client machinein a server-client network environment, or as a peer machine in adistributed (e.g., peer-to-peer) network environment. The machine 1300may be a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a cellular telephone, asmartphone, a set-top box (STB), a personal digital assistant (PDA), aweb appliance, a network router, a network switch, a network bridge, anengine control unit, integrated vehicle entertainment and informationsystem (e.g., in-dash navigation+information+radio controller), or anymachine capable of executing the instructions 1324, sequentially orotherwise, that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute the instructions 1324 to perform all or part of any oneor more of the methodologies discussed herein.

The machine 1300 includes a processor 1302 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 1304, and a static memory 1306, which areconfigured to communicate with each other via a bus 1308. The processor1302 may contain microcircuits that are configurable, temporarily orpermanently, by some or all of the instructions 1324 such that theprocessor 1302 is configurable to perform any one or more of themethodologies described herein, in whole or in part. For example, a setof one or more microcircuits of the processor 1302 may be configurableto execute one or more modules (e.g., software modules) describedherein.

The machine 1300 may further include a graphics display 1310 (e.g., aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, a cathode ray tube (CRT), orany other display capable of displaying graphics or video). The machine1300 may also include an alphanumeric input device 1312 (e.g., akeyboard or keypad), a cursor control device 1314 (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, an eye trackingdevice, or other pointing instrument), a storage unit 1316, an audiogeneration device 1318 (e.g., a sound card, an amplifier, a speaker, aheadphone jack, or any suitable combination thereof), and a networkinterface device 1320.

The storage unit 1316 includes the machine-readable medium 1322 (e.g., atangible and non-transitory machine-readable storage medium) on whichare stored the instructions 1324 embodying any one or more of themethodologies or functions described herein. The instructions 1324 mayalso reside, completely or at least partially, within the main memory1304, within the processor 1302 (e.g., within the processor's cachememory), or both, before or during execution thereof by the machine1300. Accordingly, the main memory 1304 and the processor 1302 may beconsidered machine-readable media (e.g., tangible and non-transitorymachine-readable media). The instructions 1324 may be transmitted orreceived over the network 1390 via the network interface device 1320.For example, the network interface device 1320 may communicate theinstructions 1324 using any one or more transfer protocols (e.g.,hypertext transfer protocol (HTTP)).

In some example embodiments, the machine 1300 may be a portablecomputing device, such as a smart phone, tablet computer, or wearabledevice (e.g., Google Glass), and have one or more additional inputcomponents 1330 (e.g., sensors or gauges). Examples of such inputcomponents 1330 include an image input component (e.g., one or morecameras), an audio input component (e.g., a microphone), a directioninput component (e.g., a compass), a location input component (e.g., aglobal positioning system (GPS) receiver), an orientation component(e.g., a gyroscope), a motion detection component (e.g., one or moreaccelerometers), an altitude detection component (e.g., an altimeter),and a gas detection component (e.g., a gas sensor). Inputs harvested byany one or more of these input components 1330 may be accessible andavailable for use by any of the modules described herein.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 1322 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions 1324. The term “machine-readable medium” shall also betaken to include any medium, or combination of multiple media, that iscapable of storing the instructions 1324 for execution by the machine1300, such that the instructions 1324, when executed by one or moreprocessors of the machine 1300 (e.g., processor 1302), cause the machine1300 to perform any one or more of the methodologies described herein,in whole or in part. Accordingly, a “machine-readable medium” refers toa single storage apparatus or device, as well as cloud-based storagesystems or storage networks that include multiple storage apparatus ordevices. The term “machine-readable medium” shall accordingly be takento include, but not be limited to, one or more tangible (e.g.,non-transitory) data repositories in the form of a solid-state memory,an optical medium, a magnetic medium, or any suitable combinationthereof.

Furthermore, the machine-readable medium is non-transitory in that itdoes not embody a propagating signal. However, labeling the tangiblemachine-readable medium as “non-transitory” should not be construed tomean that the medium is incapable of movement—the medium should beconsidered as being transportable from one physical location to another.Additionally, since the machine-readable medium is tangible, the mediummay be considered to be a machine-readable device.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute softwaremodules (e.g., code stored or otherwise embodied on a machine-readablemedium or in a transmission medium), hardware modules, or any suitablecombination thereof. A “hardware module” is a tangible (e.g.,non-transitory) unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an ASIC. A hardware module may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwaremodule may include software encompassed within a general-purposeprocessor or other programmable processor. It will be appreciated thatthe decision to implement a hardware module mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, and such a tangible entity may bephysically constructed, permanently configured (e.g., hardwired), ortemporarily configured (e.g., programmed) to operate in a certain manneror to perform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software(e.g., a software module) may accordingly configure one or moreprocessors, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. As used herein,“processor-implemented module” refers to a hardware module in which thehardware includes one or more processors. Moreover, the one or moreprocessors may also operate to support performance of the relevantoperations in a “cloud computing” environment or as a “software as aservice” (SaaS). For example, at least some of the operations may beperformed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain operations may be distributed among the oneor more processors, not only residing within a single machine, butdeployed across a number of machines. In some example embodiments, theone or more processors or processor-implemented modules may be locatedin a single geographic location (e.g., within a home environment, anoffice environment, or a server farm). In other example embodiments, theone or more processors or processor-implemented modules may bedistributed across a number of geographic locations.

Some portions of the subject matter discussed herein may be presented interms of algorithms or symbolic representations of operations on datastored as bits or binary digital signals within a machine memory (e.g.,a computer memory). Such algorithms or symbolic representations areexamples of techniques used by those of ordinary skill in the dataprocessing arts to convey the substance of their work to others skilledin the art. As used herein, an “algorithm” is a self-consistent sequenceof operations or similar processing leading to a desired result. In thiscontext, algorithms and operations involve physical manipulation ofphysical quantities. Typically, but not necessarily, such quantities maytake the form of electrical, magnetic, or optical signals capable ofbeing stored, accessed, transferred, combined, compared, or otherwisemanipulated by a machine. It is convenient at times, principally forreasons of common usage, to refer to such signals using words such as“data,” “content,” “bits,” “values,” “elements,” “symbols,”“characters,” “terms,” “numbers,” “numerals,” or the like. These words,however, are merely convenient labels and are to be associated withappropriate physical quantities.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or any suitable combination thereof), registers, orother machine components that receive, store, transmit, or displayinformation. Furthermore, unless specifically stated otherwise, theterms “a” or “an” are herein used, as is common in patent documents, toinclude one or more than one instance. Finally, as used herein, theconjunction “or” refers to a non-exclusive “or,” unless specificallystated otherwise.

I claim:
 1. A system to diagnose failure in a vehicle, the systemcomprising: at least one processor and executable instructionsaccessible on a computer-readable medium that, when executed, cause theat least one processor to perform operations comprising: receiving amaintenance message, over a network at a network-based marketplace, themaintenance message including characterization information received froma component in the vehicle, the component including a sensor that sensesa first part to generate the characterization information; identifyingsub-system processing rules based on the maintenance message andexecuting the sub-system processing rules, the sub-system processingrules causing a smart component engine to perform operations comprising:identifying a sub-system and scanning the sub-system responsive toidentifying an increase in a likelihood of failure of the first partbased on the characterization information, the first sub-systemincluding a plurality of parts and the scanning including scanning theplurality of parts to retrieve the characterization information from theplurality of parts to identify original equipment authenticationinformation.
 2. The system of claim 1, wherein the maintenance messageincludes part log information including a timestamp, thecharacterization information being received by a mobile device from acomponent in the vehicle, the component including a sensor that sensesthe first part to generate the characterization information based on asense of the first part, as sensed by the sensor, and to communicate thecharacterization information to the mobile device and the operationsfurther comprising: identifying user profile information, at thenetwork-based marketplace, based on the maintenance message, the userprofile information being associated with a first user on thenetwork-based marketplace and the mobile device; storing the part loginformation in the user profile information at the network-basedmarketplace; comparing the part log information that corresponds to thefirst part in the user profile information, at the network basedmarketplace, with corresponding part maintenance information to generatea service level for the first part; receiving a triggering event, at thenetwork-based marketplace, the triggering event including themaintenance message; processing the triggering event responsive toreceipt of the triggering event, the processing the triggering eventincluding the identifying the sub-system processing rules; identifyingwhether a derivative of the part log information, with respect to time,exceeds a threshold; registering in a database at least one part of theplurality of parts as not being original equipment by utilizing at leastone public key to decrypt a portion of the characterization informationretrieved from a first plurality of parts from the plurality of parts;and communicating a user interface, over the network, to the mobiledevice, the user interface including original equipment authenticationinformation to facilitate a diagnosis of a complex failure in thevehicle.
 3. The system of claim 2, wherein the threshold is dynamicallycalculated.
 4. The system of claim 2, wherein the threshold ispredetermined.
 5. The system of claim 2, further comprising identifyinga second part on the vehicle and registering the second part, in theuser profile information, wherein the second part was manufactured toinclude a sensor.
 6. The system of claim 5, wherein the sensor on thesecond part operates to sense an elasticity of the second part, andwherein the second part is an engine belt.
 7. The system of claim 5,authenticating the second part as authentic based on original equipmentmanufacturer tracking information.
 8. The system of claim 1, wherein thecharacterization information includes a percentage of wear of the firstpart and further comprising identifying whether an aggregate of thepercentage of wear of the first part is greater than a predeterminedthreshold.
 9. The system of claim 1, wherein the maintenance messageincludes vehicle identification information that identifies a make andmodel of the vehicle.
 10. A method to diagnose failure in a vehicle, themethod comprising: receiving a maintenance message, over a network at anetwork-based marketplace, the maintenance message includingcharacterization information received from a component in the vehicle,the component including a sensor that senses a first part to generatethe characterization information; identifying sub-system processingrules based on the maintenance message and executing the sub-systemprocessing rules, the sub-system processing rules causing a smartcomponent engine to perform operations comprising: identifying asub-system and scanning the sub-system responsive to identifying anincrease in a likelihood of failure of the first part based on thecharacterization information, the first sub-system including a pluralityof parts and the scanning including scanning the plurality of parts toretrieve the characterization information from the plurality of parts toidentify original equipment authentication information.
 11. The methodof claim 10, wherein the maintenance message includes part loginformation including a timestamp, the characterization informationbeing received by a mobile device from a component in the vehicle, thecomponent including a sensor that senses the first part to generate thecharacterization information based on a sense of the first part, assensed by the sensor, and to communicate the characterizationinformation to the mobile device and the method further comprises:identifying user profile information, at the network-based marketplace,based on the maintenance message, the user profile information beingassociated with a first user on the network-based marketplace and themobile device; storing the part log information in the user profileinformation at the network-based marketplace; comparing the part loginformation that corresponds to the first part in the user profileinformation, at the network based marketplace, with corresponding partmaintenance information to generate a service level for the first part;receiving a triggering event, at the network-based marketplace, thetriggering event including the maintenance message; processing thetriggering event responsive to receipt of the triggering event, theprocessing the triggering event including the identifying the sub-systemprocessing rules; identifying whether a derivative of the part loginformation, with respect to time, exceeds a threshold; registering in adatabase at least one part of the plurality of parts as not beingoriginal equipment by utilizing at least one public key to decrypt aportion of the characterization information retrieved from a firstplurality of parts from the plurality of parts; and communicating a userinterface, over the network, to the mobile device, the user interfaceincluding original equipment authentication information to facilitate adiagnosis of a complex failure in the vehicle.
 12. The method of claim11, wherein the threshold is dynamically calculated.
 13. The method ofclaim 11, wherein the threshold is predetermined.
 14. The method ofclaim 11, further comprising identifying a second part on the vehicleand registering the second part in the user profile information, whereinthe second part was manufactured to include a sensor.
 15. The method ofclaim 14, wherein the sensor on the second part operates to sense anelasticity of the second part, and wherein the second part is an enginebelt.
 16. The method of claim 14, further comprising authenticating thesecond part as authentic based on original equipment manufacturertracking information.
 17. The method of claim 10, wherein thecharacterization information includes a percentage of wear of the firstpart and the method further comprises identifying whether an aggregateof the percentage of wear of the first part is greater than apredetermined threshold.
 18. The method of claim 10, wherein themaintenance message includes vehicle identification information thatidentifies a make and model of the vehicle.
 19. A machine-readablehardware storage device having no transitory signals storing a set ofinstructions that, when executed by a processor of a machine, cause themachine to perform operations comprising: receiving a maintenancemessage, over a network at a network-based marketplace, the maintenancemessage including characterization information received from a componentin a vehicle, the component including a sensor that senses a first partto generate the characterization information; identifying sub-systemprocessing rules based on the maintenance message and executing thesub-system processing rules, the sub-system processing rules causing asmart component engine to perform operations comprising: identifying asub-system and scanning the sub-system responsive to identifying anincrease in a likelihood of failure of the first part based on thecharacterization information, the first sub-system including a pluralityof parts and the scanning including scanning the plurality of parts toretrieve the characterization information from the plurality of parts toidentify original equipment authentication information.
 20. Themachine-readable hardware storage device of claim 19, wherein thecharacterization information includes a percentage of wear of the firstpart and further comprising identifying whether an aggregate of thepercentage of wear of the first part is greater than a predeterminedthreshold.